 |
|
| If you can't view the Datasheet, Please click here to try to view without PDF Reader . |
|
|
|
| If you can't view the Datasheet, Please click here to try to view without PDF Reader . |
|
|
| Datasheet File OCR Text: |
| omap5910 dual-core processor data manual literature number: sprs197b august 2002 ? revised august 2003 literature number: sprs197b august 2002 ? revised august 2003
important notice texas instruments incorporated and its subsidiaries (ti) reserve the right to make corrections, modifications, enhancements, improvements, and other changes to its products and services at any time and to discontinue any product or service without notice. customers should obtain the latest relevant information before placing orders and should verify that such information is current and complete. all products are sold subject to ti?s terms and conditions of sale supplied at the time of order acknowledgment. ti warrants performance of its hardware products to the specifications applicable at the time of sale in accordance with ti?s standard warranty. testing and other quality control techniques are used to the extent ti deems necessary to support this warranty. except where mandated by government requirements, testing of all parameters of each product is not necessarily performed. ti assumes no liability for applications assistance or customer product design. customers are responsible for their products and applications using ti components. to minimize the risks associated with customer products and applications, customers should provide adequate design and operating safeguards. ti does not warrant or represent that any license, either express or implied, is granted under any ti patent right, copyright, mask work right, or other ti intellectual property right relating to any combination, machine, or process in which ti products or services are used. information published by ti regarding third-party products or services does not constitute a license from ti to use such products or services or a warranty or endorsement thereof. use of such information may require a license from a third party under the patents or other intellectual property of the third party, or a license from ti under the patents or other intellectual property of ti. reproduction of information in ti data books or data sheets is permissible only if reproduction is without alteration and is accompanied by all associated warranties, conditions, limitations, and notices. reproduction of this information with alteration is an unfair and deceptive business practice. ti is not responsible or liable for such altered documentation. resale of ti products or services with statements different from or beyond the parameters stated by ti for that product or service voids all express and any implied warranties for the associated ti product or service and is an unfair and deceptive business practice. ti is not responsible or liable for any such statements. following are urls where you can obtain information on other texas instruments products and application solutions: products applications amplifiers amplifier.ti.com audio www.ti.com/audio data converters dataconverter.ti.com automotive www.ti.com/automotive dsp dsp.ti.com broadband www.ti.com/broadband interface interface.ti.com digital control www.ti.com/digitalcontrol logic logic.ti.com military www.ti.com/military power mgmt power.ti.com optical networking www.ti.com/opticalnetwork microcontrollers microcontroller.ti.com security www.ti.com/security telephony www.ti.com/telephony video & imaging www.ti.com/video wireless www.ti.com/wireless mailing address: texas instruments post office box 655303 dallas, texas 75265 copyright ? 2003, texas instruments incorporated revision history iii august 2002 ? revised august 2003 sprs197b revision history this data sheet revision history highlights the technical changes made to the sprs197a device-specific data sheet to make it an sprs197b revision. scope: this document has been reviewed for technical accuracy; the technical content is up-to-date as of the specified release date and includes the following changes. page(s) no. additions/changes/deletions title page replaced ?product preview? description with ?production data? description. important notice replaced ?important notice? page. all removed ?product preview? banners from page margins. 1 revised ?usb2.0 host interface? to read ?usb (full/low speed) host interface? and ?usb2.0 function interface? to read ?usb (full speed) function interface?. 4 added paragraph that reads ?in table 2?1, signals with multiplexed functions are highlighted in gray. signals with a multiplexed pin name are separated with forward slashes as follows:? 7 replaced figure 2?2. 7 added the following note below figure 2?2: ?the gdy package has not been released to production and is still in product preview phase.? 7 removed paragraph that reads ?figure 2?2 illustrates the ball locations for the 289-ball gdy ball grid array (bga) package and is used in conjun ction with table 2?1 to locate signal names and ball grid numbers. gdy bga ball numbers in table 2?2 are read from left-to-right, top-to-bottom.? 20?32 table 2?4: deleted ?or 48 mhz? from bclk description. changed signal type from o to i on the configuration input (conf) and usb.vbus signals. changed signal type from o to i on the usb.vbus signal. 35 revised ?usb2.0 host interface? to read ?usb host interface? and ?usb2.0 function interface? to read ?usb function interface?. 43 deleted sentence that read ?this is necessary because of the large number of integrated peripherals on the omap5910 device? from paragraph 3.5.4. 44 deleted 2.0 from usb host controller in paragraph 3.6.1. also revised first paragraph to indicate the controller is usb compliant. 45 deleted 2.0 from usb host controller in paragraph 3.6.2. 50 changed note from ?dsr and dtr are not available on uart1 and uart3? to ?dsr and dtr are only available on uart1 and uart3?. 104 replaced note in section 5.1. 109 changed 30 ? to 60 ? in second paragraph of section 5.6.2. 120 updated table 5?13. 121 replaced figure 5?12 and figure 5?13. 137 updated the mmc.clk from low to high in table 5?29. revision history iv august 2002 ? revised august 2003 sprs197b contents v august 2002 ? revised august 2003 sprs197b contents section page 1 omap5910 features 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 introduction 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.1 description 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.1.1 tms320c55x dsp core 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.1.2 ti-enhanced ti925t risc processor 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2 terminal assignments 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3 terminal characteristics and multiplexing 10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.4 signal description 20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 functional overview 33 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1 functional block diagram features 34 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2 mpu memory maps 36 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2.1 mpu global memory map 36 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2.2 mpu subsystem registers memory map 37 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3 dsp memory maps 38 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.1 dsp global memory map 38 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.2 on-chip dual-access ram (daram) 39 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.3 on-chip single-access ram (saram) 39 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.4 dsp i/o space memory map 40 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.4 dsp external memory (managed by mmu) 41 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.5 mpu and dsp private peripherals 43 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.5.1 timers 43 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.5.2 32k timer (mpu only) 43 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.5.3 watchdog timer 43 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.5.4 interrupt handlers 43 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.5.5 lcd controller 43 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.6 mpu public peripherals 44 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.6.1 usb host controller 44 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.6.2 usb function peripheral 45 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.6.3 multichannel buffered serial port (mcbsp) 45 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.6.4 i 2 c master/slave interface 46 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.6.5 microwire serial interface 46 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.6.6 multimedia card/secure digital (mmc/sd) interface 46 . . . . . . . . . . . . . . . . . . . . . . . . . 3.6.7 hdq/1-wire interface 47 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.6.8 camera interface 47 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.6.9 mpuio/keyboard interface 47 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.6.10 pulse-width light (pwl) 47 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.6.11 pulse-width tone (pwt) 47 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.6.12 led pulse generator 48 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.6.13 real-time clock 48 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.6.14 frame adjustment counter 48 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.7 dsp public peripherals 48 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.7.1 multichannel buffered serial port (mcbsp) 48 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.7.2 multichannel serial interface (mcsi) 49 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . contents vi august 2002 ? revised august 2003 sprs197b section page 3.8 shared peripherals 49 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.8.1 universal asynchronous receiver/transmitter (uart) 49 . . . . . . . . . . . . . . . . . . . . . . . 3.8.2 general-purpose i/o (gpio) 50 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.8.3 mailbox registers 50 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.9 system dma controller 51 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.10 dsp dma controller 52 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.11 traffic controller (memory interfaces) 52 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.12 interprocessor communication 53 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.12.1 mpu/dsp mailbox registers 53 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.12.2 mpu interface (mpui) 53 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.12.3 mpu/dsp shared memory 54 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.13 dsp hardware accelerators 54 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.13.1 dct/idct accelerator 54 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.13.2 motion estimation accelerator 54 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.13.3 pixel interpolation accelerator 54 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.14 power supply connection examples 55 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.14.1 core and i/o voltage supply connections 55 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.14.2 core voltage noise isolation 56 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.15 mpu register descriptions 57 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.15.1 mpu private peripheral registers 58 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.15.2 mpu public peripheral registers 65 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.15.3 mpu configuration registers 74 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.16 dsp register descriptions 81 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.16.1 dsp private peripheral registers 81 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.16.2 dsp public peripheral registers 87 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.16.3 dsp configuration registers 92 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.16.4 mpu/dsp shared peripheral register descriptions 94 . . . . . . . . . . . . . . . . . . . . . . . . . . 3.17 interrupts 99 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 documentation support 103 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1 device and development-support tool nomenclature 103 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 electrical specifications 104 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.1 absolute maximum ratings 104 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.2 recommended operating conditions 105 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.3 electrical characteristics over recommended operating case temperature range (unless otherwise noted) 106 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4 package thermal resistance characteristics 107 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.5 timing parameter symbology 107 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.6 clock specifications 108 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.6.1 32-khz oscillator and input clock 108 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.6.2 base oscillator (12 mhz or 13 mhz) and input clock 109 . . . . . . . . . . . . . . . . . . . . . . . . . 5.6.3 internal clock speed limitations 110 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.7 reset timings 111 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.7.1 omap5910 device reset 111 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.7.2 omap5910 mpu core reset 112 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . contents vii august 2002 ? revised august 2003 sprs197b section page 5.8 external memory interface timing 113 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.8.1 emifs/flash interface timing 113 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.8.2 emiff/sdram interface timing 120 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.9 multichannel buffered serial port (mcbsp) timings 124 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.9.1 mcbsp transmit and receive timings 124 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.9.2 mcbsp as spi master or slave timing 128 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.10 multichannel serial interface (mcsi) 132 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.11 camera interface timings 134 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.12 lcd controller timings 135 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.13 multimedia card/secure digital (mmc/sd) timings 137 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.14 i 2 c timings 139 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.15 universal serial bus (usb) timings 140 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.16 microwire interface timings 141 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.17 hdq/1-wire interface timings 142 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 glossary 144 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 mechanical data 147 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.1 gzg ball grid array mechanical data 147 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.2 gdy ball grid array mechanical data 148 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . figures viii august 2002 ? revised august 2003 sprs197b list of figures figure page 2?1 omap5910 gzg microstar bga package (bottom view) 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2?2 omap5910 gdy package (bottom view) 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3?1 omap5910 functional block diagram 33 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3?2 dsp mmu off 41 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3?3 dsp mmu on 42 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3?4 supply connections for a typical system 55 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3?5 supply connections for a system with 1.8-v sdram 56 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3?6 external rc circuit for dpll cv dd noise isolation 57 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5?1 3.3-v test load circuit 107 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5?2 32-khz oscillator external crystal 108 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5?3 32-khz input clock 109 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5?4 internal system oscillator external crystal 109 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5?5 device reset timings 111 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5?6 mpu core reset timings 112 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5?7 asynchronous memory read timing 115 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5?8 asynchronous 32-bit read 116 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5?9 asynchronous read ? page mode rom 117 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5?10 asynchronous memory write timing 118 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5?11 synchronous burst read 119 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5?12 32-bit (2 x 16-bit) sdram rd (read) command (active row) 121 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5?13 32-bit (2 x 16-bit) sdram wrt (write) command (active row) 121 . . . . . . . . . . . . . . . . . . . . . . . . . . . 5?14 sdram actv (activate row) command 122 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5?15 sdram dcab (precharge/deactivate row) command 122 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5?16 sdram refr (refresh) command 123 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5?17 sdram mrs (mode register set) command 123 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5?18 mcbsp receive timings 127 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5?19 mcbsp transmit timings 127 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5?20 mcbsp timing as spi master or slave: clkstp = 10b, clkxp = 0 128 . . . . . . . . . . . . . . . . . . . . . . . . 5?21 mcbsp timing as spi master or slave: clkstp = 11b, clkxp = 0 129 . . . . . . . . . . . . . . . . . . . . . . . . 5?22 mcbsp timing as spi master or slave: clkstp = 10b, clkxp = 1 130 . . . . . . . . . . . . . . . . . . . . . . . . 5?23 mcbsp timing as spi master or slave: clkstp = 11b, clkxp = 1 131 . . . . . . . . . . . . . . . . . . . . . . . . 5?24 mcsi master mode timings 133 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5?25 mcsi slave mode timings 133 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5?26 camera interface timings 134 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5?27 tft mode (lcd.hs/lcd.vs on falling and lcd.px on rising lcd.pclk) 135 . . . . . . . . . . . . . . . . . . 5?28 tft mode (lcd.hs/lcd.vs on rising and lcd.px on falling lcd.pclk) 136 . . . . . . . . . . . . . . . . . . figures ix august 2002 ? revised august 2003 sprs197b figure page 5?29 mmc/sd host command timings 137 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5?30 mmc/sd card response timings 137 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5?31 mmc/sd host write timings 138 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5?32 mmc/sd host read and card crc status timings 138 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5?33 i 2 c timings 139 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5?34 usb integrated transceiver interface timings 140 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5?35 microwire timings 141 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5?36 omap5910 hdq interface reading from hdq slave device 143 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5?37 omap5910 hdq interface writing to hdq slave device 143 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5?38 typical communication between omap5910 hdq and hdq slave 143 . . . . . . . . . . . . . . . . . . . . . . . . . 5?39 hdq/1-wire break (reset) timing 143 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7?1 omap5910 289-ball microstar bga plastic ball grid array (gzg) package 147 . . . . . . . . . . . . . . . . . 7?2 omap5910 289-ball plastic ball grid array (gdy) package 148 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . tables x august 2002 ? revised august 2003 sprs197b list of tables table page 2?1 gzg bga terminal assignments 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2?2 gdy bga terminal assignments 8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2?3 terminal characteristics and multiplexing 11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2?4 signal description 20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3?1 omap5910 mpu global memory map 36 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3?2 mpu private peripheral registers 37 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3?3 mpu public peripheral registers 37 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3?4 mpu/dsp shared peripheral registers 37 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3?5 dsp public peripheral registers (accessible via mpui port) 38 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3?6 mpu configuration registers 38 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3?7 dsp global memory map 38 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3?8 daram blocks 39 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3?9 saram blocks 39 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3?10 dsp private peripheral registers 40 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3?11 dsp public peripheral registers 40 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3?12 dsp/mpu shared peripheral registers 40 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3?13 dsp configuration registers 40 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3?14 mpu timer 1 registers 58 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3?15 mpu timer 2 registers 58 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3?16 mpu timer 3 registers 58 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3?17 mpu watchdog timer registers 58 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3?18 mpu level 1 interrupt handler registers 59 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3?19 mpu level 2 interrupt handler registers 60 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3?20 system dma controller registers 61 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3?21 lcd controller registers 64 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3?22 mcbsp2 registers 66 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3?23 microwire registers 66 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3?24 i 2 c registers 67 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3?25 hdq/1-wire interface registers 67 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3?26 mmc/sd registers 68 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3?27 usb function registers 69 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3?28 usb host controller registers 71 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3?29 camera interface registers 71 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3?30 mpu i/o/keyboard registers 72 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3?31 pwl registers 72 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3?32 pwt registers 72 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3?33 led pulse generator 1 registers 72 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3?34 led pulse generator 2 registers 72 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3?35 32k timer registers 72 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3?36 real-time clock registers 73 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3?37 frame adjustment counter registers 73 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3?38 omap 5910 pin configuration registers 75 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3?39 local bus control registers 75 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3?40 local bus mmu registers 76 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3?41 dsp mmu registers 77 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . tables xi august 2002 ? revised august 2003 sprs197b table page 3?42 mpui registers 77 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3?43 tipb (private) bridge 1 configuration registers 77 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3?44 tipb (public) bridge 2 configuration registers 78 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3?45 mpu uart tipb bus switch registers 78 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3?46 traffic controller registers 79 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3?47 mpu clock/reset/power mode control registers 79 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3?48 dpll1 register 79 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3?49 ultra low-power device module registers 80 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3?50 device die identification registers 80 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3?51 jtag identification code register 80 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3?52 dsp dma controller registers 82 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3?53 dsp timer 1 registers 85 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3?54 dsp timer 2 registers 85 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3?55 dsp timer 3 registers 85 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3?56 dsp watchdog timer registers 85 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3?57 dsp interrupt interface registers 85 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3?58 dsp level 2 interrupt handler registers 86 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3?59 mcbsp1 registers 87 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3?60 mcbsp3 registers 88 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3?61 mcsi1 registers 90 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3?62 mcsi2 registers 91 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3?63 dsp instruction cache registers 92 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3?64 dsp emif configuration register 92 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3?65 dsp tipb bridge configuration registers 92 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3?66 dsp uart tipb bus switch registers 93 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3?67 dsp clock mode registers 93 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3?68 uart1 registers 95 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3?69 uart2 registers 96 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3?70 uart3/irda registers 97 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3?71 mpu/dsp shared gpio registers 98 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3?72 mpu/dsp shared mailbox registers 98 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3?73 mpu level 1 and level 2 interrupt mappings 99 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3?74 dsp level 1 interrupt mappings 101 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3?75 dsp level 2 interrupt mappings 102 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5?1 thermal resistance characteristics 107 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5?2 32-khz oscillator switching characteristics 108 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5?3 32-khz input clock timing requirements 109 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5?4 base oscillator switching characteristics 110 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5?5 internal clock speed limitations 110 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5?6 omap5910 device reset timing requirements 111 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5?7 omap5910 device reset switching characteristics 111 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5?8 mpu_rst timing requirements 112 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5?9 mpu_rst switching characteristics 112 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5?10 emifs/flash interface timing requirements 113 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5?11 emifs/flash interface switching characteristics 114 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5?12 emiff/sdram interface timing requirements 120 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . tables xii august 2002 ? revised august 2003 sprs197b table page 5?13 emiff/sdram interface switching characteristics 120 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5?14 mcbsp timing requirements 124 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5?15 mcbsp switching characteristics 126 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5?16 mcbsp as spi master or slave timing requirements (clkstp = 10b, clkxp = 0) 128 . . . . . . . . . . 5?17 mcbsp as spi master or slave switching characteristics (clkstp = 10b, clkxp = 0) 128 . . . . . . 5?18 mcbsp as spi master or slave timing requirements (clkstp = 11b, clkxp = 0) 129 . . . . . . . . . . 5?19 mcbsp as spi master or slave switching characteristics (clkstp = 11b, clkxp = 0) 129 . . . . . . . 5?20 mcbsp as spi master or slave timing requirements (clkstp = 10b, clkxp = 1) 130 . . . . . . . . . . 5?21 mcbsp as spi master or slave switching characteristics (clkstp = 10b, clkxp = 1) 130 . . . . . . 5?22 mcbsp as spi master or slave timing requirements (clkstp = 11b, clkxp = 1) 131 . . . . . . . . . . 5?23 mcbsp as spi master or slave switching characteristics (clkstp = 11b, clkxp = 1) 131 . . . . . . . 5?24 mcsi timing requirements 132 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5?25 mcsi switching characteristics 132 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5?26 camera interface timing requirements 134 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5?27 lcd controller switching characteristics 135 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5?28 mmc/sd timing requirements 137 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5?29 mmc/sd switching characteristics 137 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5?30 i 2 c signals (i2c.sda and i2c.scl) switching characteristics 139 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5?31 usb integrated transceiver interface switching characteristics 140 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5?32 microwire timing requirements 141 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5?33 microwire switching characteristics 141 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5?34 hdq/1-wire timing requirements 142 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5?35 hdq/1-wire switching characteristics 142 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . features 1 august 2002 ? revised august 2003 sprs197b 1 omap5910 features low-power, high-performance cmos technology ? 0.13- m technology ? 1.6-v core voltage ti925t (mpu) arm9tdmi ? core ? support 32-bit and 16-bit (thumb ? mode) instruction sets ? 16k-byte instruction cache ? 8k-byte data cache ? data and program memory management units (mmus) ? two 64-entry translation look-aside buffers (tlbs) for mmus ? 17-word write buffer tms320c55x ? (c55x ? ) dsp core ? one/two instructions executed per cycle ? dual multipliers (two multiply- accumulates per cycle) ? two arithmetic/logic units ? one internal program bus ? five internal data/operand buses (3 read buses and 2 write buses) ? 32k x 16-bit on-chip dual-access ram (daram) (64k bytes) ? 48k x 16-bit on-chip single-access ram (saram) (96k bytes) ? 16k x 16-bit on-chip rom (32k bytes) ? instruction cache (24k bytes) ? video hardware accelerators for dct, idct, pixel interpolation, and motion estimation for video compression 192k bytes of shared internal sram memory traffic controller (tc) ? 16-bit emifs external memory interface to access up to 128m bytes of flash, rom, or asram ? 16-bit emiff external memory interface to access up to 64m bytes of sdram 9-channel system dma controller dsp memory management unit endianism conversion logic digital phase-locked loop (dpll) for mpu/dsp/tc clocking control dsp peripherals ? three 32-bit timers and watchdog timer ? level1/level2 interrupt handlers ? six-channel dma controller ? two multichannel buffered serial ports ? two multichannel serial interfaces ti925t peripherals ? three 32-bit timers and watchdog timer ? 32-khz timer ? level1/level2 interrupt handlers ? usb (full/low speed) host interface with up to 3 ports ? usb (full speed) function interface ? one integrated usb transceiver for either host or function ? multichannel buffered serial port ? inter-integrated circuit (i 2 c) master and slave interface ? microwire ? serial interface ? multimedia card (mmc) and secure digital (sd) interface ? hdq/1-wire ? interface ? camera interface for cmos sensors ? etm9 trace module for ti925t debug ? keyboard matrix interface (6 x 5 or 8 x 8) ? up to ten mpu general-purpose i/os ? pulse-width tone (pwt) interface ? pulse-width light (pwl) interface ? two led pulse generators (lpgs) ? real-time clock (rtc) ? lcd controller with dedicated system dma channel shared peripherals ? three universal asynchronous receiver/transmitters (uarts) (one supporting sir mode for irda) ? four interprocessor mailboxes ? up to 14 shared general-purpose i/os individual power-saving modes for mpu/dsp/tc on-chip scan-based emulation logic ieee std 1149.1 ? (jtag) boundary scan logic two 289-ball ball grid array package options (gzg and gdy suffixes) tms320c55x and c55x are trademarks of texas instruments. arm9tdmi is a trademark of arm limited. thumb is a registered trademark of arm limited. microwire is a trademark of national semiconductor corporation. 1-wire is a registered trademark of dallas semiconductor corporation. ? ieee standard 1149.1-1990 standard test-access port and boundary scan architecture. introduction 2 august 2002 ? revised august 2003 sprs197b 2 introduction this section describes the main features of the omap5910 device, lists the terminal assignments, and describes the function of each terminal. this data manual also provides a detailed description section, electrical specifications, parameter measurement information, and mechanical data about the available packaging. 2.1 description the omap5910 is a highly integrated hardware and software platform, designed to meet the application processing needs of next-generation embedded devices. the omap ? platform enables oems and odms to quickly bring to market devices featuring rich user interfaces, high processing performance, and long battery life through the maximum flexibility of a fully integrated mixed processor solution. the dual-core architecture provides benefits of both dsp and risc technologies, incorporating a tms320c55x dsp core and a high-performance ti925t arm core. the omap5910 device is designed to run leading open and embedded risc-based operating systems, as well as the texas instruments (ti) dsp/bios ? software kernel foundation, and is available in a 289-ball microstar bga package. the omap5910 is targeted at the following applications: ? applications processing devices ? mobile communications ? 802.11 ? bluetooth ? wireless technology ? gsm (including gprs and edge) ? cdma ? proprietary government and other ? video and image processing (mpeg4, jpeg, windows ? media video, etc.) ? advanced speech applications (text-to-speech, speech recognition) ? audio processing (mpeg-1 audio layer3 [mp3], amr, wma, aac, and other gsm speech codecs) ? graphics and video acceleration ? generalized web access ? data processing (fax, encryption/decryption, authentication, signature verification and watermarking) 2.1.1 tms320c55x dsp core the dsp core of the omap5910 device is based on the tms320c55x dsp generation cpu processor core. the c55x dsp architecture achieves high performance and low power through increased parallelism and total focus on reduction in power dissipation. the cpu supports an internal bus structure composed of one program bus, three data read buses, two data write buses, and additional buses dedicated to peripheral and dma activity. these buses provide the ability to perform up to three data reads and two data writes in a single cycle. in parallel, the dma controller can perform up to two data transfers per cycle independent of the cpu activity. omap and dsp/bios are trademarks of texas instruments. bluetooth is a trademark owned by bluetooth sig, inc. windows is a registered trademark of microsoft corporation. other trademarks are the property of their respective owners. introduction 3 august 2002 ? revised august 2003 sprs197b the c55x cpu provides two multiply-accumulate (mac) units, each capable of 17-bit x 17-bit multiplication in a single cycle. a central 40-bit arithmetic/logic unit (alu) is supported by an additional 16-bit alu. use of the alus is under instruction set control, providing the ability to optimize parallel activity and power consumption. these resources are managed in the address unit (au) and data unit (du) of the c55x cpu. the c55x dsp generation supports a variable byte width instruction set for improved code density. the instruction unit (iu) performs 32-bit program fetches from internal or external memory and queues instructions for the program unit (pu). the program unit decodes the instructions, directs tasks to au and du resources, and manages the fully protected pipeline. predictive branching capability avoids pipeline flushes on execution of conditional instructions. the omap5910 dsp core also includes a 24k-byte instruction cache to minimize external memory accesses, improving data throughput and conserving system power. 2.1.1.1 dsp tools support the 55x dsp core is supported by the industry?s leading expressdsp ? software environment including the code composer studio ? integrated development environment, dsp/bios software kernel foundation, the tms320 ? dsp algorithm standard, and the industry?s largest third-party network. code composer studio features code generation tools including a c-compiler, visual linker, simulator, real-time data exchange (rtdx ? ), xds510 ? emulation device drivers, and chip support libraries (csl). dsp/bios is a scalable real-time software foundation available for no cost to users of texas instruments? dsp products providing a preemptive task scheduler and real-time analysis capabilities with very low memory and megahertz overhead. the tms320 dsp algorithm standard is a specification of coding conventions allowing fast integration of algorithms from different teams, sites, or third parties into the application framework. texas instruments? extensive dsp third-party network of over 400 providers brings focused competencies and complete solutions to customers. 2.1.1.2 dsp software support texas instruments has also developed foundation software available for the 55x dsp core. the c55x dsp library (dsplib) features over 50 c-callable software kernels (fir/iir filters, fast fourier t ransforms (ffts), and various computational functions). the dsp image/video processing library (imglib) contains over 20 software kernels highly optimized for c55x dsps and is compiled with the latest revision of the c55x dsp code generation tools. these imaging functions support a wide range of applications that include compression, video processing, machine vision, and medical imaging. 2.1.2 ti-enhanced ti925t risc processor the mpu core is a ti925t reduced instruction set computer (risc) processor. the ti925t is a 32-bit processor core that performs 32-bit or 16-bit instructions and processes 32-bit, 16-bit, or 8-bit data. the core uses pipelining so that all parts of the processor and memory system can operate continuously. the mpu core incorporates: ? a coprocessor 15 (cp15) and protection module ? data and program memory management units (mmus) with table look-aside buffers. ? a separate 16k-byte instruction cache and 8k-byte data cache. both are two-way associative with virtual index virtual tag (vivt). ? a 17-word write buffer (wb) the omap5910 device uses the ti925t core in little endian mode only. to reduce effective memory access time, the ti925t has an instruction cache, a data cache, and a write buffer. in general, these are transparent to program execution. expressdsp, code composer studio, tms320, rtdx, and xds510 are trademarks of texas instruments. introduction 4 august 2002 ? revised august 2003 sprs197b 2.2 terminal assignments figure 2?1 illustrates the ball locations for the 289-ball gzg ball grid array (bga) package and is used in conjunction with t able 2?1 to locate signal names and ball grid numbers. gzg bga ball numbers in t able 2?1 are read from left-to-right, top-to-bottom. 8 l b a 1 f d c e h k g j 3 24 7 5 6 r m p n v t u w aa y 15 11 9 10 13 12 14 18 17 16 21 19 20 figure 2?1. omap5910 gzg microstar bga ? package (bottom view) in table 2?1, signals with multiplexed functions are highlighted in gray. signals with a multiplexed pin name are separated with forward slashes as follows: ? signal1/signal2/signal3 (for example, gpio11/hdq) signals which are associated with specific peripherals are denoted by using the peripheral name, followed by a period, and then the signal name; as follows: ? peripheral1.signal1 (for example, mcbsp1.dr) table 2?1. gzg bga terminal assignments gzg bga ball # signal gzg bga ball # signal gzg bga ball # signal gzg bga ball # signal a1 dv dd4 a2 sdram.ras a3 cv dd1 a5 dv dd4 a7 dv dd4 a9 cv dd a11 v ss a13 v ss a15 dv dd1 a17 lcd.p[13] a19 dv dd1 a20 lcd.p[5] a21 v ss b1 v ss b2 v ss b3 sdram.dqml b4 sdram.d[13] b5 v ss b6 sdram.d[8] b7 v ss b8 sdram.d[4] b9 sdram.d[0] b10 dv dd4 b12 dv dd4 b13 cv dd3 b14 sdram.a[0] b15 lcd.ac b16 v ss b17 lcd.p[11] b18 v ss b19 lcd.p[6] b20 cv dd3 b21 lcd.p[1] c1 flash.a[3] c2 dv dd5 c3 sdram.we c4 sdram.d[14] c5 sdram.d[11] c6 sdram.d[9] c7 sdram.d[6] c8 sdram.d[2] c9 sdram.clk c10 sdram.ba[0] c11 sdram.a[10] c12 sdram.a[7] c13 sdram.a[4] c14 sdram.a[1] c15 lcd.pclk microstar bga is a trademark of texas instruments. introduction 5 august 2002 ? revised august 2003 sprs197b table 2?1. gzg bga terminal assignments (continued) gzg bga ball # signal gzg bga ball # signal gzg bga ball # signal gzg bga ball # signal c16 lcd.p[14] c17 lcd.p[10] c18 lcd.p[7] c19 lcd.p[2] c20 kb.c[5] c21 kb.c[4] d2 flash.a[5] d3 flash.a[2] d4 sdram.dqmu d5 sdram.d[15] d6 sdram.d[12] d7 sdram.d[7] d8 sdram.d[5] d9 sdram.cke d10 sdram.ba[1] d11 sdram.a[9] d12 sdram.a[6] d13 sdram.a[3] d14 lcd.vs d15 lcd.p[15] d16 lcd.p[9] d17 lcd.p[8] d18 lcd.p[0] d19 kb.c[2] d20 kb.c[1] e1 dv dd5 e2 v ss e3 flash.a[7] e4 flash.a[4] e5 rsvd e18 kb.c[3] e19 kb.r[4] e20 kb.r[3] e21 dv dd1 f2 cv dd f3 flash.a[9] f4 flash.a[6] f18 kb.c[0] f19 kb.r[1] f20 v ss g1 v ss g2 flash.a[12] g3 flash.a[11] g4 flash.a[10] g8 sdram.d[3] g9 sdram.d[1] g10 sdram.a[12] g11 sdram.a[8] g12 sdram.a[2] g13 lcd.p[12] g14 lcd.p[3] g18 kb.r[0] g19 pwron_reset g20 mcbsp1.clks g21 mcbsp1.clkx h2 dv dd5 h3 flash.a[15] h4 flash.a[14] h7 flash.rdy h8 sdram.d[10] h9 sdram.cas h10 sdram.a[11] h11 sdram.a[5] h12 lcd.hs h13 lcd.p[4] h14 kb.r[2] h15 mcbsp1.fsx/ mcbsp1.dx h18 mcbsp1.dx/ mcbsp1.fsx h19 cam.exclk/ etm.sync/ uwire.sdo h20 mcbsp1.dr j1 flash.a[20] j2 flash.a[17] j3 flash.a[19] j4 flash.a[18] j7 flash.a[8] j8 flash.a[1] j14 cam.d[5]/ etm.d[5]/ uwire.sdi j15 cam.lclk/ etm.clk/ uwire.sclk j18 cam.d[7]/ etm.d[7]/ uwire.cs0 j19 cam.d[6]/ etm.d[6]/ uwire.cs3 j20 v ss j21 cv dd3 k2 v ss k3 flash.a[23] k4 flash.a[22] k7 flash.a[16] k8 flash.a[13] k14 cam.d[1]/etm.d[1]/ uart3.rts k15 cam.d[2]/ etm.d[2]/ uart3.cts k18 cam.d[4]/ etm.d[4]/ uart3.tx k19 cam.d[3]/ etm.d[3]/ uart3.rx k20 v ss l1 dv dd5 l3 flash.be[0] l4 flash.adv l7 flash.a[24] l8 flash.a[21] l14 uart3.rx/pwl/ uart2.rx l15 cam.hs/ etm.pstat[1]/ uart2.cts l18 cam.vs/ etm.pstat[2] l19 cam.d[0]/ etm.d[0]/ mpuio12 l21 dv dd1 m2 cv dd4 m3 flash.cs1 m4 flash.cs2 / flash.baa m7 flash.cs0 m8 flash.be[1] m14 gpio2/ spi.clk m15 gpio7/ mmc.dat2 m18 uart3.tx/ pwt/ uart2.tx m19 cam.rstz/ etm.pstat[0]/ uart2.rts m20 gpio15/ kb.r[7] n1 v ss n2 flash.d[1] n3 flash.clk n4 flash.d[0] n7 flash.d[2] n8 flash.cs3 n14 uwire.cs0 / mcbsp3.clkx n15 mpuio2/ ext_dma_req0 n18 gpio12/ mcbsp3.fsx n19 gpio13/ kb.r[5] n20 gpio11/ hdq n21 gpio14/ kb.r[6] p2 flash.d[3] p3 dv dd5 p4 flash.d[4] p7 flash.d[5] p8 flash.d[11] p9 usb0.dp p10 mcbsp2.dr/ mcbsp2.dx p11 mmc.cmd/spi.do introduction 6 august 2002 ? revised august 2003 sprs197b table 2?1. gzg bga terminal assignments (continued) gzg bga ball # signal gzg bga ball # signal gzg bga ball # signal gzg bga ball # signal p12 cv dd p13 clk32k_in p14 rst_host_out/ mcbsp3.dx/ usb1.se0 p15 uwire.cs3 / kb.c[6] p18 gpio3/ spi.cs3/ mcbsp3.fsx/led1 p19 gpio6/ spi.cs1/ mcbsp3.fsx p20 gpio4/ spi.cs2/ mcbsp3.fsx r1 dv dd5 r2 flash.d[6] r3 flash.d[7] r4 flash.d[8] r8 usb.dm r9 uart2.rx/ usb2.vm r10 mclkreq/ext_ master_req r11 mmc.dat0/spi.di r12 osc32k_out r13 bclkreq/ uart3.cts/ uart1.dsr r14 uart1.cts r18 gpio0/ spi.rdy/ usb.vbus r19 gpio1/ uart3.rts r20 cv dd3 r21 v ss t2 flash.d[9] t3 flash.d[10] t4 flash.d[14] t18 i2c.scl t19 mpuio4/ ext_dma_req1 / led2 t20 mpuio5/ low_pwr u1 flash.d[12] u2 v ss u3 flash.d[13] u4 flash.oe u18 uwire.sdi/ uart3.dsr/ uart1.dsr/ mcbsp3.dr u19 mpuio1 u20 v ss u21 dv dd1 v2 dv dd5 v3 flash.d[15] v4 flash.wp v5 v ss v6 uart2.tx/ usb2.txd v7 mcbsp2.clkr/ gpio11 v8 mpuio3 v9 mcsi2.sync/ gpio7 v10 mmc.dat1/ mpuio7 v11 mmc.clk v12 v ss v13 mcsi1.sync/ usb1.vp v14 uart1.rx v15 mpu_rst v16 emu0 v17 tms v18 conf v19 uwire.sclk/ kb.c[7] v20 i2c.sda w1 flash.rp w2 flash.we w3 osc1_out w4 usb.puen/ usb.clko w5 uart2.rts/ usb2.se0/ mpuio5 w6 mcbsp2.fsr/ gpio12 w7 mcbsp2.fsx w8 gpio9 w9 mcsi2.dout/ usb2.txen w10 mmc.dat2/ mpuio11 w11 mmc.dat3/ mpuio6 w12 osc32k_in w13 mcsi1.din/ usb1.rcv w14 mcsi1.dout/ usb1.txd w15 rst_out w16 mcbsp3.clkx/ usb1.txen w17 emu1 w18 tck w19 bfail/ ext_fiq w20 v ss w21 uwire.sdo/ uart3.dtr/ uart1.dtr/ mcbsp3.dx y1 cv dd2 y2 osc1_in y3 v ss y4 uart2.bclk y5 uart2.cts/ usb2.rcv/ gpio7 y6 mcbsp2.clkx y7 dv dd3 y8 gpio8 y9 mclk y10 mcsi2.clk/ usb2.susp y12 clk32k_out/ mpuio0/ usb1.speed y13 bclk/ uart3.rts/ uart1.dtr y14 uart1.tx y15 v ss y16 dv dd1 y17 stat_val/ wkup y18 trst y19 tdi y20 cv dd y21 cv dda aa1 v ss aa2 dv dd2 aa3 cv dd2 aa5 mcbsp2.dx/ mcbsp2.dr introduction 7 august 2002 ? revised august 2003 sprs197b table 2?1. gzg bga terminal assignments (continued) gzg bga ball # signal gzg bga ball # signal gzg bga ball # signal gzg bga ball # signal aa7 v ss aa9 mcsi2.din/ usb2.vp aa11 dv dd1 aa13 mcsi1.clk/ usb1.vm aa15 uart1.rts aa17 mpu_boot/ mcbsp3.dr/ usb1.susp aa19 tdo aa20 clk32k_ctrl aa21 v ss figure 2?2 illustrates the ball locations for the 289-ball gdy ball grid array (bga) package and is used in conjunction with table 2?1 to locate signal names and ball grid numbers. gdy bga ball numbers in figure 2?2 are read from left-to-right, top-to-bottom. a 1 2 b 4 3 6 5 8 7 10 9 12 11 14 13 16 15 17 c d e f g h j k l m n p r t u bottom view note: the gdy package has not been released to production and is still in product preview phase. figure 2?2. omap5910 gdy package (bottom view) in table 2?2, signals with multiplexed functions are highlighted in gray. signals within a multiplexed pin name are separated with forward slashes as follows: ? signal1/signal2/signal3 (for example, gpio11/hdq) signals which are associated with specific peripherals are denoted by using the peripheral name, followed by a period, and then the signal name; as follows: ? peripheral1.signal1 (for example, mcbsp1.dr) introduction 8 august 2002 ? revised august 2003 sprs197b table 2?2. gdy bga terminal assignments gdy bga ball # signal gdy bga ball # signal gdy bga ball # signal gdy bga ball # signal a1 sdram.we a2 sdram.dqmu a3 sdram.d[9] a4 sdram.d[6] a5 dv dd4 a6 sdram.d[0] a7 sdram.clk a8 sdram.a[9] a9 sdram.a[5] a10 sdram.a[1] a11 lcd.ac a12 lcd.pclk a13 lcd.p[9] a14 dv dd1 a15 lcd.p[6] a16 lcd.p[3] a17 kb.c[5] b1 flash.a[1] b2 sdram.dqml b3 cv dd1 b4 sdram.d[12] b5 sdram.d[11] b6 sdram.d[5] b7 sdram.d[2] b8 sdram.ba[0] b9 sdram.a[11] b10 sdram.a[2] b11 sdram.a[0] b12 lcd.p[13] b13 lcd.p[11] b14 lcd.p[7] b15 lcd.p[4] b16 lcd.p[0] b17 kb.c[3] c1 flash.a[3] c2 flash.a[4] c3 flash.rdy c4 sdram.ras c5 sdram.d[14] c6 sdram.d[10] c7 sdram.d[3] c8 sdram.a[12] c9 sdram.ba[1] c10 sdram.a[8] c11 sdram.a[3] c12 dv dd1 c13 lcd.p[14] c14 lcd.p[8] c15 lcd.p[5] c16 lcd.p[1] c17 kb.c[0] d1 dv dd5 d2 flash.a[7] d3 dv dd4 d4 sdram.d[15] d5 dv dd4 d6 sdram.d[7] d7 sdram.cke d8 dv dd4 d9 sdram.a[6] d10 sdram.a[4] d11 lcd.vs d12 lcd.p[15] d13 kb.r[0] d14 kb.r[1] d15 lcd.p[2] d16 kb.c[4] d17 kb.r[4] e1 flash.a[12] e2 cv dd e3 flash.a[5] e4 flash.a[6] e5 v ss e6 sdram.d[8] e7 sdram.d[1] e8 cv dd e9 sdram.a[10] e10 dv dd4 e11 lcd.hs e12 lcd.p[10] e13 v ss e14 dv dd1 e15 kb.c[2] e16 kb.c[1] e17 kb.r[3] f1 dv dd5 f2 flash.a[11] f3 flash.a[9] f4 flash.a[10] f5 flash.a[8] f6 v ss f7 sdram.d[4] f8 sdram.cas f9 sdram.a[7] f10 cv dd3 f11 lcd.p[12] f12 v ss f13 mcbsp1.clks f14 pwron_reset f15 kb.r[2] f16 mcbsp1.fsx/ mcbsp1.dx f17 mcbsp1.dx/ mcbsp1.fsx g1 flash.a[16] g2 flash.a[17] g3 flash.a[14] g4 flash.a[13] g5 flash.a[15] g6 flash.a[2] g7 v ss g8 sdram.d[13] g9 v ss g10 cv dd3 g11 v ss g12 cam.d[6]/ etm.d[6]/ uwire.cs3 g13 cam.exclk/ etm.sync/ uwire.sdo g14 cam.d[7]/ etm.d[7]/ uwire.cs0 g15 mcbsp1.clkx g16 mcbsp1.dr g17 cam.d[3]/ etm.d[3]/ uart3.rx h1 flash.adv h2 flash.a[20] h3 flash.a[18] h4 flash.a[19] h5 flash.a[21] h6 flash.a[22] h7 dv dd5 h8 v ss h9 v ss h10 v ss h11 cv dd3 h12 uart3.rx/pwl/ uart2.rx h13 dv dd1 h14 cam.d[1]/etm.d[1]/ uart3.rts h15 cam.lclk/ etm.clk/ uwire.sclk h16 cam.d[5]/ etm.d[5]/ uwire.sdi h17 cam.d[2]/ etm.d[2]/ uart3.cts j1 flash.be[1] j2 flash.cs0 j3 flash.a[24] j4 flash.a[23] j5 flash.be[0] j6 v ss j7 v ss j8 v ss j9 v ss j10 v ss j11 v ss j12 v ss introduction 9 august 2002 ? revised august 2003 sprs197b table 2?2. gdy bga terminal assignments (continued) gdy bga ball # signal gdy bga ball # signal gdy bga ball # signal gdy bga ball # signal j13 uart3.tx/ pwt/ uart2.tx j14 cam.rstz/ etm.pstat[0]/ uart2.rts j15 cam.d[4]/ etm.d[4]/ uart3.tx j16 cam.d[0]/ etm.d[0]/ mpuio12 j17 cam.vs/ etm.pstat[2] k1 flash.cs1 k2 cv dd4 k3 flash.d[1] k4 flash.clk k5 flash.cs2 / flash.baa k6 dv dd5 k7 cv dd2 k8 v ss k9 v ss k10 v ss k11 cv dd3 k12 gpio3/ spi.cs3/ mcbsp3.fsx/led1 k13 gpio6/ spi.cs1/ mcbsp3.fsx k14 gpio13/ kb.r[5] k15 cam.hs/ etm.pstat[1]/ uart2.cts k16 gpio15/ kb.r[7] k17 gpio14/ kb.r[6] l1 flash.cs3 l2 dv dd5 l3 dv dd5 l4 flash.d[2] l5 flash.d[0] l6 flash.d[3] l7 v ss l8 cv dd2 l9 v ss l10 bclkreq/ uart3.cts/ uart1.dsr l11 v ss l12 uwire.cs3 / kb.c[6] l13 mpuio5/ low_pwr l14 gpio4/ spi.cs2/ mcbsp3.fsx l15 gpio12/ mcbsp3.fsx l16 gpio11/ hdq l17 gpio7/ mmc.dat2 m1 flash.d[4] m2 flash.d[5] m3 flash.d[11] m4 flash.d[6] m5 flash.d[7] m6 v ss m7 uart2.rx/ usb2.vm m8 gpio9 m9 mmc.dat1/ mpuio7 m10 uart1.cts m11 rst_out m12 v ss m13 uwire.sclk/ kb.c[7] m14 mpuio1 m15 gpio2/ spi.clk m16 gpio0/ spi.rdy/ usb.vbus m17 gpio1/ uart3.rts n1 flash.d[9] n2 flash.d[13] n3 flash.oe n4 flash.d[8] n5 v ss n6 uart2.cts/ usb2.rcv/ gpio7 n7 dv dd3 n8 mclkreq/ ext_master_req n9 clk32k_in n10 clk32k_out/ mpuio0/ usb1.speed n11 rsvd n12 mcsi1.dout/ usb1.txd n13 v ss n14 i2c.sda n15 mpuio4/ ext_dma_req1 / led2 n16 dv dd1 n17 mpuio2/ ext_dma_req0 p1 flash.d[10] p2 flash.we p3 osc1_out p4 usb.dm p5 usb0.dp p6 mcbsp2.fsr/ gpio12 p7 mpuio3 p8 mcsi2.din/ usb2.vp p9 dv dd1 p10 cv dd p11 bclk/ uart3.rts/ uart1.dtr p12 mpu_rst p13 uart1.tx p14 mcbsp3.clkx/ usb1.txen p15 i2c.scl introduction 10 august 2002 ? revised august 2003 sprs197b table 2?2. gdy bga terminal assignments (continued) gdy bga ball # signal gdy bga ball # signal gdy bga ball # signal gdy bga ball # signal p16 uwire.sdo/ uart3.dtr/ uart1.dtr/ mcbsp3.dx p17 uwire.sdi/ uart3.dsr/ uart1.dsr/ mcbsp3.dr r1 flash.d[12] r2 osc1_in r3 flash.wp r4 uart2.tx/ usb2.txd r5 mcbsp2.dx/ mcbsp2.dr r6 mcbsp2.dr/ mcbsp2.dx r7 mcsi2.sync/ gpio7 r8 mmc.dat2/ mpuio11 r9 mmc.dat3/ mpuio6 r10 mcsi1.din/ usb1.rcv r11 uart1.rx r12 mpu_boot/ mcbsp3.dr/ usb1.susp r13 tms r14 bfail/ ext_fiq r15 cv dda r16 uwire.cs0 / mcbsp3.clkx r17 emu0 t1 flash.d[14] t2 flash.rp t3 usb.puen/ usb.clko t4 uart2.bclk t5 mcbsp2.clkr/ gpio11 t6 mcbsp2.fsx t7 mcsi2.dout/ usb2.txen t8 mcsi2.clk/ usb2.susp t9 osc32k_out t10 osc32k_in t11 mcsi1.sync/ usb1.vp t12 dv dd1 t13 emu1 t14 tck t15 clk32k_ctrl t16 conf t17 cv dd u1 dv dd5 u2 flash.d[15] u3 dv dd2 u4 uart2.rts/ usb2.se0/ mpuio5 u5 mcbsp2.clkx u6 gpio8 u7 mclk u8 mmc.cmd/spi.do u9 mmc.dat0/spi.di u10 mmc.clk u11 mcsi1.clk/ usb1.vm u12 uart1.rts u13 rst_host_out/ mcbsp3.dx/ usb1.se0 u14 stat_val/ wkup u15 trst u16 tdo u17 tdi 2.3 terminal characteristics and multiplexing table 2?3 describes terminal characteristics and the signals multiplexed on each ball. the table column headers are explained below: ? signal name: the names of all the signals that are multiplexed on each ball. ? type: the terminal type when a particular signal is multiplexed on the terminal. ? mux ctrl setting: the register field that controls multiplexing on the terminal and the proper register field setting necessary to select the signal to be multiplexed on the terminal. the reset values of these register fields are indicated in bold type. ? deselected input st ate: the logic level internally driven to the signal when it is not selected to be multiplexed on the corresponding terminal. ? pullup/pulldn: denotes the presence of an internal pullup or pulldown. pullups and pulldowns can be enabled or disabled via software. ? buffer strength: drive strength of the associated output buffer. ? other: contains various terminal information, such as buffer type, boundary scan capability, and gating/inhibit functionality. certain terminals may be gated or 3-stated based on the state of other terminals and/or software configuration register settings. introduction 11 august 2002 ? revised august 2003 sprs197b ? reset state: the state of the terminal at reset. ? supply: the voltage supply which powers the terminal?s i/o buffers. note: due to the extensive pin multiplexing options which are available on the omap5910 device, a software utility is available to ease the process of configuring the pins based on the peripheral set required by a specific application. the 5910 omap pin configuration utility is currently available from texas instruments. note: configuring two pins to the same input signal is not supported as it can yield unexpected results. this can be easily avoided with proper software configuration. table 2?3. terminal characteristics and multiplexing gzg ball gdy ball signal name type ? mux ctrl setting ? deselected input state pu/ pd buffer strength other ? reset state # supply c3 a1 sdram.we o/z na na 4 ma a 1 dv dd4 a2 c4 sdram.ras o/z na na 4 ma a 1 dv dd4 d4 a2 sdram.dqmu o/z na na 4 ma a 1 dv dd4 b3 b2 sdram.dqml o/z na na 4 ma a 1 dv dd4 d5 c4 b4 d6 c5 h8 c6 b6 d7 c7 d8 b8 g8 c8 g9 b9 d4 c5 g8 b4 b5 c6 a3 e6 d6 a4 b6 f7 c7 b7 e7 a6 sdram.d[15:0] i/o/z na na 4 ma e 0 dv dd4 d9 d7 sdram.cke o/z na na 4 ma a 1 dv dd4 c9 a7 sdram.clk i/o/z na na 8 ma e lz dv dd4 h9 f8 sdram.cas o/z na na 4 ma a 1 dv dd4 d10 c10 c9 b8 sdram.ba[1:0] o/z na na 4 ma a 0 dv dd4 g10 h10 c11 d11 g11 c12 d12 h11 c13 d13 g12 c14 b14 c8 b9 e9 a8 c10 f9 d9 a9 d10 c11 b10 a10 b11 sdram.a[12:0] o/z na na 4 ma a 0 dv dd4 d14 d11 lcd.vs o na na 4 ma j, a, g1 0 dv dd1 ? i = input, o = output, z = high-impedance ? ?regx? denotes the terminal multiplexing register that controls the specified terminal where regx = func_mux_ctrl_x pd20 = 20- a internal pulldown, pd100 = 100- a pulldown, pu20 = 20- a internal pullup, pu100 = 100- a internal pullup ? a = standard lvcmos input/output g1 = terminal may be gated by bfail b = fail-safe lvcmos input/output g2 = terminal may be gated by gpio9 and mpuio3 c = usb transceiver input/output g3 = terminal may be gated by bfail and pwron_reset d = i 2 c input/output buffers h1 = terminal may be 3-stated by bfail input e = fail-safe lvcmos input and standard lvcmos output j = boundary-scannable terminal f = analog oscillator terminals # z = high-impedance, lz = low-impedance (pin is driven), 1 = output driven high, 0 = output driven low || uart1 signals can be multiplexed to this pin via additional multiplexing in the usb module. introduction 12 august 2002 ? revised august 2003 sprs197b table 2?3. terminal characteristics and multiplexing (continued) supply reset state # other ? buffer strength pu/ pd deselected input state mux ctrl setting ? type ? signal name gdy ball gzg ball h12 e11 lcd.hs o na na 4 ma j, a, g1 0 dv dd1 b15 a11 lcd.ac o na na 4 ma j, a, g1 0 dv dd1 c15 a12 lcd.pclk o na na 4 ma j, a, g1 0 dv dd1 d15 c16 a17 g13 b17 c17 d16 d17 c18 b19 a20 h13 g14 c19 b21 d18 d12 c13 b12 f11 b13 e12 a13 c14 b14 a15 c15 b15 a16 d15 c16 b16 lcd.p[15:0] o na na 4 ma j, a, g1 0 dv dd1 c20 c21 e18 d19 d20 f18 a17 d16 b17 e15 e16 c17 kb.c[5:0] o na na 4 ma a, j 0 dv dd1 e19 e20 h14 f19 g18 d17 e17 f15 d14 d13 kb.r[4:0] i na na a, j input dv dd1 g19 f14 pwron_reset i na na b, j input dv dd1 g20 f13 mcbsp1.clks i na na b, j input dv dd1 g21 g15 mcbsp1.clkx i/o/z na na 4 ma j, b, g1 z dv dd1 h15 f17 mcbsp1.fsx i/o/z reg4[14:12] = 000 0 4 ma j, b, g1 z dv dd1 h15 f17 mcbsp1.dx o reg4[14:12] = 001 na 4 ma j, b, g1 z dv dd1 h18 f16 mcbsp1.dx o reg4[17:15] = 000 na 4 ma j, b, g1 0 dv dd1 h18 f16 mcbsp1.fsx i/o/z reg4[17:15] = 001 0 4 ma j, b, g1 0 dv dd1 h20 g16 mcbsp1.dr i na na pd20 b , j input dv dd1 h19 g13 cam.exclk o reg4[23:21] = 000 na 8 ma j, a, g1 0 dv dd1 h19 g13 etm.sync o reg4[23:21] = 001 na 8 ma j, a, g1 0 dv dd1 uwire.sdo o reg4[23:21] = 010 na j15 h15 cam.lclk i reg4[26:24] = 000 0 8 ma b, j input dv dd1 j15 h15 etm.clk o reg4[26:24] = 001 na 8 ma b, j input dv dd1 uwire.sclk o reg4[26:24] = 010 na ? i = input, o = output, z = high-impedance ? ?regx? denotes the terminal multiplexing register that controls the specified terminal where regx = func_mux_ctrl_x pd20 = 20- a internal pulldown, pd100 = 100- a pulldown, pu20 = 20- a internal pullup, pu100 = 100- a internal pullup ? a = standard lvcmos input/output g1 = terminal may be gated by bfail b = fail-safe lvcmos input/output g2 = terminal may be gated by gpio9 and mpuio3 c = usb transceiver input/output g3 = terminal may be gated by bfail and pwron_reset d = i 2 c input/output buffers h1 = terminal may be 3-stated by bfail input e = fail-safe lvcmos input and standard lvcmos output j = boundary-scannable terminal f = analog oscillator terminals # z = high-impedance, lz = low-impedance (pin is driven), 1 = output driven high, 0 = output driven low || uart1 signals can be multiplexed to this pin via additional multiplexing in the usb module. introduction 13 august 2002 ? revised august 2003 sprs197b table 2?3. terminal characteristics and multiplexing (continued) supply reset state # other ? buffer strength pu/ pd deselected input state mux ctrl setting ? type ? signal name gdy ball gzg ball j18 g14 cam.d[7] i reg4[29:27] = 000 na 8 ma b, j input dv dd1 j18 g14 etm.d[7] o reg4[29:27] = 001 na 8 ma b, j input dv dd1 uwire.cs0 o reg4[29:27] = 010 na j19 g12 cam.d[6] i reg5[2:0] = 000 na 8 ma b, j input dv dd1 j19 g12 etm.d[6] o reg5[2:0] = 001 na 8 ma b, j input dv dd1 uwire.cs3 o reg5[2:0] = 010 na j14 h16 cam.d[5] i reg5[5:3] = 000 na 8 ma b, j input dv dd1 j14 h16 etm.d[5] o reg5[5:3] = 001 na 8 ma b, j input dv dd1 uwire.sdi i reg5[5:3] = 010 na pd20 k18 j15 cam.d[4] i reg5[8:6] = 000 na 8 ma b, j input dv dd8 k18 j15 etm.d[4] o reg5[8:6] = 001 na 8 ma b, j input dv dd8 uart3.tx o reg5[8:6] = 010 na k19 g17 cam.d[3] i reg5[11:9] = 000 na 8 ma b, j input dv dd1 k19 g17 etm.d[3] o reg5[11:9] = 001 na 8 ma b, j input dv dd1 uart3.rx i reg5[11:9] = 010 na pd20 k15 h17 cam.d[2] i reg5[14:12] = 000 na 8 ma b, j input dv dd1 k15 h17 etm.d[2] o reg5[14:12] = 001 na 8 ma b, j input dv dd1 uart3.cts i reg5[14:12] = 010 na pd20 k14 h14 cam.d[1] i reg5[17:15] = 000 na 8 ma b, j input dv dd1 k14 h14 etm.d[1] o reg5[17:15] = 001 na 8 ma b, j input dv dd1 uart3.rts o reg5[17:15] = 010 na l19 j16 cam.d[0] i reg5[20:18] = 000 na 8 ma b, j input dv dd1 l19 j16 etm.d[0] o reg5[20:18] = 001 na 8 ma b, j input dv dd1 mpuio12 i/o/z reg5[20:18] = 010 na l18 j17 cam.vs i reg5[23:21] = 000 na 8 ma b, j input dv dd1 l18 j17 etm.pstat[2] o reg5[23:21] = 001 na 8 ma b, j input dv dd1 l15 k15 cam.hs i reg5[26:24] = 000 na 8 ma b, j input dv dd1 l15 k15 etm.pstat[1] o reg5[26:24] = 001 na 8 ma b, j input dv dd1 uart2.cts i reg5[26:24] = 010 na pd20 m19 j14 cam.rstz o reg5[29:27] = 000 na 8 ma j, b, g1 0 dv dd1 m19 j14 etm.pstat[0] o reg5[29:27] = 001 na 8 ma j, b, g1 0 dv dd1 uart2.rts o reg5[29:27] = 010 na m18 j13 pin forced to drive low o reg6[2:0] = 000 na 4 ma j, a, g1 0 dv dd1 m18 j13 uart3.tx o reg6[2:0] = 001 na 4 ma j, a, g1 0 dv dd1 pwt o reg6[2:0] = 010 na irq_obs o reg6[2:0] = 011 na uart2.tx o reg6[2:0] = 100 na ? i = input, o = output, z = high-impedance ? ?regx? denotes the terminal multiplexing register that controls the specified terminal where regx = func_mux_ctrl_x pd20 = 20- a internal pulldown, pd100 = 100- a pulldown, pu20 = 20- a internal pullup, pu100 = 100- a internal pullup ? a = standard lvcmos input/output g1 = terminal may be gated by bfail b = fail-safe lvcmos input/output g2 = terminal may be gated by gpio9 and mpuio3 c = usb transceiver input/output g3 = terminal may be gated by bfail and pwron_reset d = i 2 c input/output buffers h1 = terminal may be 3-stated by bfail input e = fail-safe lvcmos input and standard lvcmos output j = boundary-scannable terminal f = analog oscillator terminals # z = high-impedance, lz = low-impedance (pin is driven), 1 = output driven high, 0 = output driven low || uart1 signals can be multiplexed to this pin via additional multiplexing in the usb module. introduction 14 august 2002 ? revised august 2003 sprs197b table 2?3. terminal characteristics and multiplexing (continued) supply reset state # other ? buffer strength pu/ pd deselected input state mux ctrl setting ? type ? signal name gdy ball gzg ball l14 h12 uart3.rx i reg6[5:3] = 000 1 4 ma b, j input dv dd1 l14 h12 pwl o reg6[5:3] = 001 na 4 ma b, j input dv dd1 dma_req_obs o reg6[5:3] = 010 na uart2.rx i reg6[5:3] = 011 na m20 k16 gpio15 i/o/z reg6[8:6] = 000 na pd20 4 ma j, b, g1 input dv dd1 kb.r[7] i reg6[8:6] = 001 1 dd1 n21 k17 gpio14 i/o/z reg6[11:9] = 000 na pd20 4 ma j, b, g1 input dv dd1 n21 k17 kb.r[6] i reg6[11:9] = 001 1 4 ma j, b, g1 input dv dd1 n19 k14 gpio13 i/o/z reg6[14:12] = 000 na pd20 4 ma j, b, g1 input dv dd1 n19 k14 kb.r[5] i reg6[14:12] = 001 1 4 ma j, b, g1 input dv dd1 n18 l15 gpio12 i/o/z reg6[17:15] = 000 na pd20 4 ma j, b, g1 input dv dd1 n18 l15 mcbsp3.fsx i/o/z reg6[17:15] = 001 0 pd20 4 ma j, b, g1 input dv dd1 n20 l16 gpio11 i/o/z reg6[20:18] = 000 na pd20 4 ma j, b, g1 input dv dd1 n20 l16 hdq i/o reg6[20:18] = 001 na pd20 4 ma j, b, g1 input dv dd1 m15 l17 gpio7 i/o/z reg6[23:21] = 000 na pd20 4 ma j, b, g1 input dv dd1 m15 l17 mmc.dat2 i/o/z reg6[23:21] = 001 1 4 ma j, b, g1 input dv dd1 p19 k13 gpio6 i/o/z reg6[26:24] = 000 na pd20 4 ma j, b, g1 input dv dd1 p19 k13 spi.cs1 o reg6[26:24] = 001 na 4 ma j, b, g1 input dv dd1 mcbsp3.fsx i/o/z reg6[26:24] = 010 na pd20 p20 l14 gpio4 i/o/z reg6[29:27] = 000 na pd20 4 ma j, b, g1 input dv dd1 p20 l14 spi.cs2 o reg6[29:27] = 001 na 4 ma j, b, g1 input dv dd1 mcbsp3.fsx i/o/z reg6[29:27] = 010 na pd20 p18 k12 gpio3 i/o/z reg7[2:0] = 000 na pd20 4 ma j, b, g1 input dv dd1 p18 k12 spi.cs3 o reg7[2:0] = 001 na 4 ma j, b, g1 input dv dd1 mcbsp3.fsx i/o/z reg7[2:0] = 010 na pd20 led1 o reg7[2:0] = 011 na m14 m15 gpio2 i/o/z reg7[5:3] = 000 na pd20 4 ma j, b, g1 input dv dd1 m14 m15 spi.clk o reg7[5:3] = 001 na 4 ma j, b, g1 input dv dd1 r19 m17 gpio1 i/o/z reg7[8:6] = 000 na pd20 4 ma j, b, g1 input dv dd1 r19 m17 uart3.rts o reg7[8:6] = 001 na 4 ma j, b, g1 input dv dd1 r18 m16 gpio0 i/o/z reg7[11:9] = 000 na pd20 4 ma j, b, g1 input dv dd1 r18 m16 spi.rdy i reg7[11:9] = 001 na 4 ma j, b, g1 input dv dd1 usb.vbus i reg7[11:9] = 010 0 pd20 t20 l13 mpuio5 i/o/z reg7[14:12] = 000 na pd20 4 ma j, b, g1 input dv dd1 t20 l13 low_pwr o reg7[14:12] = 001 na 4 ma j, b, g1 input dv dd1 ? i = input, o = output, z = high-impedance ? ?regx? denotes the terminal multiplexing register that controls the specified terminal where regx = func_mux_ctrl_x pd20 = 20- a internal pulldown, pd100 = 100- a pulldown, pu20 = 20- a internal pullup, pu100 = 100- a internal pullup ? a = standard lvcmos input/output g1 = terminal may be gated by bfail b = fail-safe lvcmos input/output g2 = terminal may be gated by gpio9 and mpuio3 c = usb transceiver input/output g3 = terminal may be gated by bfail and pwron_reset d = i 2 c input/output buffers h1 = terminal may be 3-stated by bfail input e = fail-safe lvcmos input and standard lvcmos output j = boundary-scannable terminal f = analog oscillator terminals # z = high-impedance, lz = low-impedance (pin is driven), 1 = output driven high, 0 = output driven low || uart1 signals can be multiplexed to this pin via additional multiplexing in the usb module. introduction 15 august 2002 ? revised august 2003 sprs197b table 2?3. terminal characteristics and multiplexing (continued) supply reset state # other ? buffer strength pu/ pd deselected input state mux ctrl setting ? type ? signal name gdy ball gzg ball t19 n15 mpuio4 i/o/z reg7[17:15] = 000 na pd20 4 ma j, b, g1 input dv dd1 t19 n15 ext_dma_req1 i reg7[17:15] = 001 na 4 ma j, b, g1 input dv dd1 led2 o reg7[17:15] = 010 na n15 n17 mpuio2 i/o/z reg7[20:18] = 000 na pd20 4 ma j, b, g1 input dv dd1 n15 n17 ext_dma_req0 i reg7[20:18] = 001 na 4 ma j, b, g1 input dv dd1 u19 m14 mpuio1 i/o/z na na 4 ma b, j input dv dd1 t18 p15 i2c.scl i/o/z na na 6 ma j, d, h1 z dv dd1 v20 n14 i2c.sda i/o/z na na 6 ma j, d, h1 z dv dd1 u18 p17 uwire.sdi i reg8[2:0] = 000 na pd20 4 ma b, j input dv dd1 u18 p17 uart3.dsr i reg8[2:0] = 001 1 pd20 4 ma b, j input dv dd1 uart1.dsr i reg8[2:0] = 010 1 pd20 mcbsp3.dr i reg8[2:0] = 011 na pd20 w21 p16 uwire.sdo o reg8[5:3] = 000 na 4 ma j, a, g1 0 dv dd1 w21 p16 uart3.dtr o reg8[5:3] = 001 na 4 ma j, a, g1 0 dv dd1 uart1.dtr o reg8[5:3] = 010 na mcbsp3.dx o reg8[5:3] = 011 na v19 m13 uwire.sclk o reg8[8:6] = 000 na 4 ma j, a, g1 0 dv dd1 v19 m13 kb.c[7] o reg8[8:6] = 001 na 4 ma j, a, g1 0 dv dd1 n14 r16 pin forced to high-z z reg8[11:9] = 000 na 4 ma j, a z dv dd1 n14 r16 uwire.cs0 o reg8[11:9] = 001 na 4 ma j, a z dv dd1 mcbsp3.clkx i/o/z reg8[11:9] = 010 na p15 l12 pin forced to high-z z reg8[14:12] = 000 na 4 ma j, a z dv dd1 p15 l12 uwire.cs3 o reg8[14:12] = 001 na 4 ma j, a z dv dd1 kb.c[6] o reg8[14:12] = 010 na w19 r14 bfail/ext_fiq i na na j, b input dv dd1 aa20 t15 clk32k_ctrl i na na j, b input dv dd1 v18 t16 conf i na na pd10 0 a input dv dd1 y19 u17 tdi i na na pd20 b input dv dd1 aa19 u16 tdo o na na 4 ma a 0 dv dd1 v17 r13 tms i na na pd20 b input dv dd1 w18 t14 tck i na na pd20 b input dv dd1 y18 u15 trst i na na pd10 0 b input dv dd1 v16 r17 emu0 i/o/z na na pu10 0 2 ma b z dv dd1 w17 t13 emu1 i/o/z na na pu10 0 2 ma b z dv dd1 y17 u14 stat_val/wkup i na na a input dv dd1 ? i = input, o = output, z = high-impedance ? ?regx? denotes the terminal multiplexing register that controls the specified terminal where regx = func_mux_ctrl_x pd20 = 20- a internal pulldown, pd100 = 100- a pulldown, pu20 = 20- a internal pullup, pu100 = 100- a internal pullup ? a = standard lvcmos input/output g1 = terminal may be gated by bfail b = fail-safe lvcmos input/output g2 = terminal may be gated by gpio9 and mpuio3 c = usb transceiver input/output g3 = terminal may be gated by bfail and pwron_reset d = i 2 c input/output buffers h1 = terminal may be 3-stated by bfail input e = fail-safe lvcmos input and standard lvcmos output j = boundary-scannable terminal f = analog oscillator terminals # z = high-impedance, lz = low-impedance (pin is driven), 1 = output driven high, 0 = output driven low || uart1 signals can be multiplexed to this pin via additional multiplexing in the usb module. introduction 16 august 2002 ? revised august 2003 sprs197b table 2?3. terminal characteristics and multiplexing (continued) supply reset state # other ? buffer strength pu/ pd deselected input state mux ctrl setting ? type ? signal name gdy ball gzg ball aa17 r12 mpu_boot i reg8[29:27] = 000 na pd20 4 ma j, b input dv dd1 aa17 r12 mcbsp3_dr i reg8[29:27] = 001 na pd20 4 ma j, b input dv dd1 usb1_susp o reg8[29:27] = 010 na p14 u13 rst_host_out o reg9[2:0] = 000 na 4 ma j, a, g1 0 dv dd1 p14 u13 mcbsp3.dx o reg9[2:0] = 001 na 4 ma j, a, g1 0 dv dd1 usb1.se0 o reg9[2:0] = 010 na w16 p14 pin forced to high-z z reg9[5:3] = 000 na pd20 4 ma j, a, g1 z dv dd1 w16 p14 mcbsp3.clkx i/o/z reg9[5:3] = 001 na pd20 4 ma j, a, g1 z dv dd1 usb1.txen o reg9[5:3] = 010 na v15 p12 mpu_rst i na na j, b input dv dd1 w15 m11 rst_out o na na 4 ma j, a 0 dv dd1 aa15 u12 pin forced to drive low o reg9[14:12] = 000 na 2 ma j, a, g1 0 dv dd1 aa15 u12 uart1.rts o reg9[14:12] = 001 na 2 ma j, a, g1 0 dv dd1 r14 m10 uart1.cts i na na pd20 j, b input dv dd1 v14 r11 uart1.rx i na na pd20 j, b input dv dd1 y14 p13 pin forced to drive low o reg9[23:21] = 000 na 2 ma j, a, g1 0 dv dd1 y14 p13 uart1.tx o reg9[23:21] = 001 na 2 ma j, a, g1 0 dv dd1 w14 n12 mcsi1.dout o reg9[26:24] = 000 na 2 ma j, a, g1, h1 0 dv dd1 w14 n12 usb1.txd o reg9[26:24] = 001 na 2 ma j, a, g1, h1 0 dv dd1 uart1.tx o reg9[26:24] = 001 || na r13 l10 bclkreq i reg9[29:27] = 000 0 pd20 j, b input dv dd1 r13 l10 uart3.cts i reg9[29:27] = 001 0 pd20 j, b input dv dd1 uart1.dsr i reg9[29:27] = 010 1 pd20 y13 p11 bclk o rega[2:0] = 000 na 4 ma j, a, g1 0 dv dd1 y13 p11 uart3.rts o rega[2:0] = 001 na 4 ma j, a, g1 0 dv dd1 uart1.dtr o rega[2:0] = 010 na v13 t11 mcsi1.sync i/o/z rega[5:3] = 000 0 pd20 2 ma j, b, g1 input dv dd1 v13 t11 usb1.vp i rega[5:3] = 001 na pd20 2 ma j, b, g1 input dv dd1 aa13 u11 mcsi1.clk i/o/z rega[8:6] = 000 0 pd20 2 ma j, b, g1 input dv dd1 aa13 u11 usb1.vm i rega[8:6] = 001 0 pd20 2 ma j, b, g1 input dv dd1 uart1.rx i rega[8:6] = 001 || 0 pd20 w13 r10 mcsi1.din i rega[11:9] = 000 na pd20 j, b input dv dd1 w13 r10 usb1.rcv i rega[11:9] = 001 0 pd20 j, b input dv dd1 uart1.cts i rega[11:9] = 001 || 0 pd20 y12 n10 clk32k_out o rega[14:12] = 000 na 8 ma j, a lz dv dd1 y12 n10 mpuio0 i/o/z rega[14:12] = 001 na 8 ma j, a lz dv dd1 usb1.speed o rega[14:12] = 010 na p13 n9 clk32k_in i na na j, b input dv dd1 ? i = input, o = output, z = high-impedance ? ?regx? denotes the terminal multiplexing register that controls the specified terminal where regx = func_mux_ctrl_x pd20 = 20- a internal pulldown, pd100 = 100- a pulldown, pu20 = 20- a internal pullup, pu100 = 100- a internal pullup ? a = standard lvcmos input/output g1 = terminal may be gated by bfail b = fail-safe lvcmos input/output g2 = terminal may be gated by gpio9 and mpuio3 c = usb transceiver input/output g3 = terminal may be gated by bfail and pwron_reset d = i 2 c input/output buffers h1 = terminal may be 3-stated by bfail input e = fail-safe lvcmos input and standard lvcmos output j = boundary-scannable terminal f = analog oscillator terminals # z = high-impedance, lz = low-impedance (pin is driven), 1 = output driven high, 0 = output driven low || uart1 signals can be multiplexed to this pin via additional multiplexing in the usb module. introduction 17 august 2002 ? revised august 2003 sprs197b table 2?3. terminal characteristics and multiplexing (continued) supply reset state # other ? buffer strength pu/ pd deselected input state mux ctrl setting ? type ? signal name gdy ball gzg ball w12 t10 osc32k_in ? na na f na na r12 t9 osc32k_out ? na na f na na w11 r9 mmc.dat3 i/o/z regd[14:12] = 000 1 pu20 4 ma j, b, g1 input dv dd1 w11 r9 reserved na regd[14:12] = 001 na 4 ma j, b, g1 input dv dd1 mpuio6 i/o/z regd[14:12] = 010 na pu20 v11 u10 mmc.clk o na na 4 ma j, a, g1 0 dv dd1 r11 u9 mmc.dat0/spi.di i/o/z na na pu20 4 ma j, b, g1 input dv dd1 w10 r8 mmc.dat2 i/o/z rega[20:18] = 000 1 pu20 4 ma j, b, g1 input dv dd1 w10 r8 pin forced to hi-z z rega[20:18] = 001 na 4 ma j, b, g1 input dv dd1 mpuio11 i/o/z rega[20:18] = 010 na pu20 v10 m9 mmc.dat1 i/o/z rega[26:24] = 000 1 pu20 4 ma j, b, g1 input dv dd1 v10 m9 reserved na rega[26:24] = 001 na 4 ma j, b, g1 input dv dd1 mpuio7 i/o/z rega[26:24] = 010 na pu20 p11 u8 mmc.cmd/spi.do i/o/z na na pu10 0 4 ma j, b, g1 input dv dd1 y10 t8 mcsi2.clk i/o/z regb[5:3] = 000 0 pd20 4 ma j, e input dv dd3 y10 t8 usb2.susp o regb[5:3] = 001 na 4 ma j, e input dv dd3 aa9 p8 mcsi2.din i regb[8:6] = 000 na pd20 j, b input dv dd3 aa9 p8 usb2.vp i regb[8:6] = 001 0 pd20 j, b input dv dd3 w9 t7 mcsi2.dout o regb[11:9] = 000 na 4 ma j, a, g2 0 dv dd3 w9 t7 usb2.txen o regb[11:9] = 001 na 4 ma j, a, g2 0 dv dd3 v9 r7 mcsi2.sync i/o/z regb[14:12] = 000 0 pd20 4 ma j, e input dv dd3 v9 r7 gpio7 i/o/z regb[14:12] = 001 na pd20 4 ma j, e input dv dd3 y9 u7 mclk o na na 4 ma j, a, g1 0 dv dd3 r10 n8 mclkreq i regb[20:18] = 000 0 pd20 4 ma j, e input dv dd3 r10 n8 ext_master_req o regb[20:18] = 001 na 4 ma j, e input dv dd3 w8 m8 gpio9 i/o/z na na pd20 4 ma j, e, g3 input dv dd3 y8 u6 gpio8 i/o/z na na pd20 4 ma j, e, g3 input dv dd3 v8 p7 mpuio3 i/o/z na na pd20 4 ma j, e, g1 input dv dd3 p10 r6 mcbsp2.dr i regc[2:0] = 000 na pd20 4 ma j, b, g2 input dv dd3 p10 r6 mcbsp2.dx o regc[2:0] = 001 na 4 ma j, b, g2 input dv dd3 w7 t6 mcbsp2.fsx i/o/z na 0 pd20 4 ma j, e, g2 input dv dd3 v7 t5 mcbsp2.clkr i/o/z regc[8:6] = 000 0 4 ma j, e z dv dd3 v7 t5 gpio11 i/o/z regc[8:6] = 001 na pd20 4 ma j, e z dv dd3 y6 u5 mcbsp2.clkx i/o/z na na pd20 4 ma j, e, g2 input dv dd3 w6 p6 mcbsp2.fsr i/o/z regc[14:12] = 000 0 4 ma j, e z dv dd3 w6 p6 gpio12 i/o/z regc[14:12] = 001 na pd20 4 ma j, e z dv dd3 ? i = input, o = output, z = high-impedance ? ?regx? denotes the terminal multiplexing register that controls the specified terminal where regx = func_mux_ctrl_x pd20 = 20- a internal pulldown, pd100 = 100- a pulldown, pu20 = 20- a internal pullup, pu100 = 100- a internal pullup ? a = standard lvcmos input/output g1 = terminal may be gated by bfail b = fail-safe lvcmos input/output g2 = terminal may be gated by gpio9 and mpuio3 c = usb transceiver input/output g3 = terminal may be gated by bfail and pwron_reset d = i 2 c input/output buffers h1 = terminal may be 3-stated by bfail input e = fail-safe lvcmos input and standard lvcmos output j = boundary-scannable terminal f = analog oscillator terminals # z = high-impedance, lz = low-impedance (pin is driven), 1 = output driven high, 0 = output driven low || uart1 signals can be multiplexed to this pin via additional multiplexing in the usb module. introduction 18 august 2002 ? revised august 2003 sprs197b table 2?3. terminal characteristics and multiplexing (continued) supply reset state # other ? buffer strength pu/ pd deselected input state mux ctrl setting ? type ? signal name gdy ball gzg ball aa5 r5 mcbsp2.dx o regc[17:15] = 000 na 4 ma j, e, g2 0 dv dd3 aa5 r5 mcbsp2.dr i regc[17:15] = 001 na pd20 4 ma j, e, g2 0 dv dd3 r9 m7 uart2.rx i regc[20:18] = 000 1 pd20 4 ma j, b input dv dd3 r9 m7 usb2.vm i regc[20:18] = 001 0 pd20 4 ma j, b input dv dd3 y5 n6 uart2.cts i regc[23:21] = 000 1 pd20 4 ma j, b input dv dd3 y5 n6 usb2.rcv i regc[23:21] = 001 0 pd20 4 ma j, b input dv dd3 gpio7 i/o/z regc[23:21] = 010 na pd20 j, e w5 u4 pin forced to drive low o regc[26:24] = 000 na 4 ma j, e, g2 0 dv dd3 w5 u4 uart2.rts o regc[26:24] = 001 na 4 ma j, e, g2 0 dv dd3 usb2.se0 o regc[26:24] = 010 na mpuio5 i/o/z regc[26:24] = 011 na v6 r4 pin forced to drive low o regc[29:27] = 000 na 4 ma j, a, g2 0 dv dd3 v6 r4 uart2.tx o regc[29:27] = 001 na 4 ma j, a, g2 0 dv dd3 usb2.txd o regc[29:27] = 010 na y4 t4 uart2.bclk o na na 4 ma j, a, g2 0 dv dd3 w4 t3 usb.puen o regd[5:3] = 000 na 8 ma j, b, g1 0 dv dd2 w4 t3 usb.clko o regd[5:3] = 001 na 8 ma j, b, g1 0 dv dd2 p9 p5 usb.dp i/o/z na na 18.3 ma c z dv dd2 r8 p4 usb.dm i/o/z na na 18.3 ma c z dv dd2 y2 r2 osc1_in ? na na f na na w3 p3 osc1_out ? na na f na na v4 r3 flash.wp o/z na na 4 ma a 0 dv dd5 w2 p2 flash.we o/z na na 4 ma a 1 dv dd5 w1 t2 flash.rp o/z na na 4 ma a 0 dv dd5 u4 n3 flash.oe o/z na na 4 ma a 1 dv dd5 v3 t4 u3 u1 p8 t3 t2 r4 r3 r2 p7 p4 p2 n7 n2 n4 u2 t1 n2 r1 m3 p1 n1 n4 m5 m4 m2 m1 l6 l4 k3 l5 flash.d[15:0] i/o/z na na 4 ma e 0 dv dd5 n3 k4 flash.clk o/z na na 8 ma e, g1, h2 0 dv dd5 n8 l1 flash.cs3 o/z na na 4 ma a 1 dv dd5 ? i = input, o = output, z = high-impedance ? ?regx? denotes the terminal multiplexing register that controls the specified terminal where regx = func_mux_ctrl_x pd20 = 20- a internal pulldown, pd100 = 100- a pulldown, pu20 = 20- a internal pullup, pu100 = 100- a internal pullup ? a = standard lvcmos input/output g1 = terminal may be gated by bfail b = fail-safe lvcmos input/output g2 = terminal may be gated by gpio9 and mpuio3 c = usb transceiver input/output g3 = terminal may be gated by bfail and pwron_reset d = i 2 c input/output buffers h1 = terminal may be 3-stated by bfail input e = fail-safe lvcmos input and standard lvcmos output j = boundary-scannable terminal f = analog oscillator terminals # z = high-impedance, lz = low-impedance (pin is driven), 1 = output driven high, 0 = output driven low || uart1 signals can be multiplexed to this pin via additional multiplexing in the usb module. introduction 19 august 2002 ? revised august 2003 sprs197b table 2?3. terminal characteristics and multiplexing (continued) supply reset state # other ? buffer strength pu/ pd deselected input state mux ctrl setting ? type ? signal name gdy ball gzg ball m4 k5 flash.cs2 o/z regd[8:6] = 000 na 4 ma a 1 dv dd5 m4 k5 flash.baa o/z regd[8:6] = 001 na 4 ma a 1 dv dd5 m3 k1 flash.cs1 o/z na na 4 ma a 1 dv dd5 m7 j2 flash.cs0 o/z na na 4 ma a 1 dv dd5 m8 l3 j1 j5 flash.be[1:0] o/z na na 4 ma a 0 dv dd5 l4 h1 flash.adv o/z na na 4 ma a 1 dv dd5 l7 k3 k4 l8 j1 j3 j4 j2 k7 h3 h4 k8 g2 g3 g4 f3 j7 e3 f4 d2 e4 c1 d3 j8 j3 j4 h6 h5 h2 h4 h3 g2 g1 g5 g3 g4 e1 f2 f4 f3 f5 d2 e4 e3 c2 c1 g6 b1 flash.a[24:1] o/z na na 4 ma a, g1 0 dv dd5 h7 c3 flash.rdy i na na b input dv dd5 e5 n11 rsvd na na na na na ? i = input, o = output, z = high-impedance ? ?regx? denotes the terminal multiplexing register that controls the specified terminal where regx = func_mux_ctrl_x pd20 = 20- a internal pulldown, pd100 = 100- a pulldown, pu20 = 20- a internal pullup, pu100 = 100- a internal pullup ? a = standard lvcmos input/output g1 = terminal may be gated by bfail b = fail-safe lvcmos input/output g2 = terminal may be gated by gpio9 and mpuio3 c = usb transceiver input/output g3 = terminal may be gated by bfail and pwron_reset d = i 2 c input/output buffers h1 = terminal may be 3-stated by bfail input e = fail-safe lvcmos input and standard lvcmos output j = boundary-scannable terminal f = analog oscillator terminals # z = high-impedance, lz = low-impedance (pin is driven), 1 = output driven high, 0 = output driven low || uart1 signals can be multiplexed to this pin via additional multiplexing in the usb module. introduction 20 august 2002 ? revised august 2003 sprs197b 2.4 signal description table 2?4 provides a description of the signals on omap5910. many signals are available on multiple pins depending upon the software configuration of the pin multiplexing options. ball numbers which are italicized indicate the default pin muxings at reset. ball numbers for busses are listed from msb to lsb (left to right, top to bottom). table 2?4. signal description signal gzg ball gdy ball description type ? emiff sdram interface sdram.we c3 a1 sdram write enable. sdram.we is active (low) during writes, dcab, and mrs commands to sdram memory. o/z sdram.ras a2 c4 sdram row address strobe. sdram.ras is active (low) during actv, dcab, refr, and mrs commands to sdram memory. o/z sdram.dqmu d4 a2 sdram upper data mask. active-low data mask for the upper byte of the sdram data bus (sdram.d[15:8]). the data mask outputs allow for both 16-bit-wide and 8-bit-wide accesses to sdram memories. o/z sdram.dqml b3 b2 sdram lower data mask. active-low data mask for the lower byte of the sdram data bus (sdram.d[7:0]). the data mask outputs allow for both 16-bit-wide and 8-bit-wide accesses to sdram memories. o/z sdram.d[15:0] d5, c4, b4, d6, c5, h8, c6, b6, d7, c7, d8, b8, g8, c8, g9, b9 d4, c5, g8, b4, b5, c6, a3, e6, d6, a4, b6, f7, c7, b7, d7, a6 sdram data bus. sdram.d[15:0] provides data exchange between the traffic controller and sdram memory. i/o/z sdram.cke d9 d7 sdram clock enable. active-high output which enables the sdram clock during normal operation; sdram.cke is driven inactive to put the memory into low-power mode. o/z sdram.clk c9 a7 sdram clock. clock for synchronization sdram memory commands/accesses. to minimize voltage undershoot and overshoot effects, it is recommended to place a series resistor (typically ~33 ? ) close to the sdram.clk driver pin. i/o/z sdram.cas h9 f8 sdram column address strobe. sdram.cas is active (low) during reads, writes, and the refr and mrs commands to sdram memory. o/z sdram.ba[1:0] d10, c10 c9, b8 sdram bank address bus. provides the bank address to sdram memories. o/z ? i = input, o = output, z = high-impedance ? all core voltage supplies should be tied to the same voltage level (within 0.3 v). during system prototyping phases, it may be useful to maintain a capability for independent measurement of core supply currents to facilitate power optimization experiments. see sections 5.6.1 and 5.6.2 for special v ss considerations with oscillator circuits. introduction 21 august 2002 ? revised august 2003 sprs197b table 2?4. signal description (continued) signal type ? description gdy ball gzg ball emiff sdram interface (continued) sdram.a[12:0] g10, h10, c11, d11, g11, c12, d12, h11, c13, d13, g12, c14, b14 c8, b9, e9, a8, c10, f9, d9, a9, d10, c11, b10, a10, b11 sdram address bus. provides row and column address information to the sdram memory as well as mrs command data. sdram.a[10] also serves as a control signal to define specific commands to sdram memory. o/z emifs flash and asynchronous memory interface flash.wp v4 r3 emifs write protect. active-low output for hardware write protection feature on standard memory devices. o/z flash.we w2 p2 emifs write enable. active-low write enable output for flash or sram memories or asynchronous devices. o/z flash.rp w1 t2 emifs power down or reset output (intel ? flash devices) o/z flash.oe u4 n3 emifs output enable. active-low output enable output for flash or sram memories or asynchronous devices. o/z flash.d[15:0] v3, t4, u3, u1, p8, t3, t2, r4, r3, r2, p7, p4, p2, n7, n2, n4 u2, t1, n2, r1, m3, p1, n1, n4, m5, m4, m2, m1, l6, l4, k3, l5 emifs data bus. bidirectional 16-bit data bus used to transfer read and write data during emifs accesses. i/o/z flash.clk n3 k4 emifs clock. clock output that is active during synchronous modes of emifs operation for synchronous burst flash memories. o/z flash.cs3 n8 l1 emifs chip selects. active-low chip-select outputs that become active when the appropriate address is decoded internal to the device. each chip select decodes a o/z flash.cs2 m4 k5 emifs chip selects. active-low chip-select outputs that become active when the appropriate address is decoded internal to the device. each chip select decodes a 32m-byte region of memory space. o/z flash.cs1 m3 k1 32m-byte region of memory space. flash.cs0 m7 j2 flash.be[1:0] m8, l3 j1, j5 emifs byte enables. active-low byte enable signals used to perform byte-wide accesses to memories or devices that support byte enables. o/z flash.adv l4 h1 emifs address valid. active-low control signal used to indicate a valid address is present on the flash.a[24:1] bus. o/z flash.baa m4 k5 emifs burst advance acknowledge. active-low control signal used with advanced micro devices ? burst flash. flash.baa is multiplexed with flash.cs2 . o/z ? i = input, o = output, z = high-impedance ? all core voltage supplies should be tied to the same voltage level (within 0.3 v). during system prototyping phases, it may be useful to maintain a capability for independent measurement of core supply currents to facilitate power optimization experiments. see sections 5.6.1 and 5.6.2 for special v ss considerations with oscillator circuits. advanced micro devices is a trademark of advanced micro devices, inc. intel is a registered trademark of intel corporation. introduction 22 august 2002 ? revised august 2003 sprs197b table 2?4. signal description (continued) signal type ? description gdy ball gzg ball emifs flash and asynchronous memory interface (continued) flash.a[24:1] l7, k3, k4, l8, j1, j3, j4, j2, k7, h3, h4, k8, g2, g3, g4, f3, j7, e3, f4, d2, e4, c1, d3, j8 j3, j4, h6, h5, h2, h4, h3, g2, g1, g5, g3, g4, e1, f2, f4, f3, f5, d2, e4, e3, c2, c1, g6, b1 emifs address bus. address output bus for all emifs accesses. flash.a[24:1] provides the upper 24 bits of a 25-bit byte address. the byte enables must be used to implement 8-bit accesses. o/z flash.rdy h7 c3 emifs ready. active-high ready input used to suspend the emifs interface when the external memory or asynchronous device is not ready to continue the current cycle. it is recommended that this pin should be pulled high externally and unused. see the omap5910 dual-core processor silicon errata (literature number sprz016) for more details. i lcd interface lcd.vs d14 d11 lcd vertical sync output. lcd.vs is the frame clock which signals the start of a new frame of pixels to the lcd panel. in tft mode, lcd.vs is the vertical synchronization signal. o lcd.hs h12 e11 lcd horizontal sync. lcd.hs is the line clock which signals the end of a line of pixels to the lcd panel. in tft mode, lcd.hs is the horizontal synchronization signal. o lcd.ac b15 a11 lcd ac-bias. lcd.ac is used to signal the lcd to switch the polarity of the row and column power supplies to counteract charge buildup causing dc offset. in tft mode, lcd.ac is used as the output enable to latch lcd pixel data using the pixel clock. o lcd.pclk c15 a12 lcd pixel clock output. clock output provided to synchronize pixel data to the lcd panels. in passive mode, lcd.pclk only transitions when lcd.p[15:0] is valid. in active mode, lcd.pclk transitions continuously and lcd.ac is used as the output enable when lcd.p[15:0] is valid. o ? i = input, o = output, z = high-impedance ? all core voltage supplies should be tied to the same voltage level (within 0.3 v). during system prototyping phases, it may be useful to maintain a capability for independent measurement of core supply currents to facilitate power optimization experiments. see sections 5.6.1 and 5.6.2 for special v ss considerations with oscillator circuits. introduction 23 august 2002 ? revised august 2003 sprs197b table 2?4. signal description (continued) signal type ? description gdy ball gzg ball lcd interface (continued) lcd.p[15:0] d15, c16, a17, g13, b17, c17, d16, d17, c18, b19, a20, h13, g14, c19, b21, d18 d12, c13, b12, f11, b13, e12, a13, c14, b14, a15, c15, b15, a16, d15, c16, b16 lcd pixel data bus. pixel data is transferred on this output bus to lcd panels. o keyboard matrix interface kb.c[7:0] v19, p15, c20, c21, e18, d19, d20, f18 m13, l12, a17, d16, b17, e15, e16, c17 keyboard matrix column outputs. kb.cx column outputs are used in conjunction with the kb.rx row inputs to implement a 6x5 or 8x8 keyboard matrix. o kb.r[7:0] m20, n21, n19, e19, e20, h14, f19, g18 k16, k17, k14, d17, e17, f15, d14, d13 keyboard matrix row inputs. kb.rx row inputs are used in conjunction with the kb.cx column outputs to implement a 6x5 or 8x8 keyboard matrix. i multichannel buffered serial ports (mcbsps) mcbsp1.clks g20 f13 mcbsp1 clock source. provides external clock reference for use with transmitter or reciever. clks is only present on mcbsp1. i mcbsp1.clkx g21 g15 mcbsp transmit clock. serial shift clock reference for the transmitter. clkx is present on all mcbsps. in the case of mcbsp1 and mcbsp3, the clock input to i/o/z mcbsp2.clkx y6 u5 mcbsp transmit clock. serial shift clock reference for the transmitter. clkx is present on all mcbsps. in the case of mcbsp1 and mcbsp3, the clock input to the mcbsp receiver may also be provided on this terminal via an internal i/o/z mcbsp3.clkx w16, n14 p6, r16 the mcbsp receiver may also be provided on this terminal via an internal loop-back connection between the transmitter and receiver clocks. mcbsp1.fsx h15, h18 f17, f16 mcbsp transmit frame sync. frame synchronization for transmitter. fsx is present on all mcbsps. in the case of mcbsp1 and mcbsp3, the frame sync input to the mcbsp receiver may also be provided on this terminal via an internal i/o/z mcbsp2.fsx w7 t6 present on all mcbsps. in the case of mcbsp1 and mcbsp3, the frame sync input to the mcbsp receiver may also be provided on this terminal via an internal loop-back connection between the transmitter and receiver frame syncs. mcbsp3.fsx n18, p18, p19, p20 l15, k12, k13, l14 loop-back connection between the transmitter and receiver frame syncs. ? i = input, o = output, z = high-impedance ? all core voltage supplies should be tied to the same voltage level (within 0.3 v). during system prototyping phases, it may be useful to maintain a capability for independent measurement of core supply currents to facilitate power optimization experiments. see sections 5.6.1 and 5.6.2 for special v ss considerations with oscillator circuits. introduction 24 august 2002 ? revised august 2003 sprs197b table 2?4. signal description (continued) signal type ? description gdy ball gzg ball multichannel buffered serial ports (mcbsps) (continued) mcbsp1.dx h18, h15 f16, f17 mcbsp transmit data. serial transmit data output. dx is present on all mcbsps. o mcbsp2.dx aa5, p10 r5, r6 mcbsp3.dx p14, w21 u13, p16 mcbsp2.clkr v7 t5 mcbsp2 receive clock. serial shift clock reference for the receiver. clkr is only present on mcbsp2. i/o/z mcbsp2.fsr w6 p6 mcbsp2 receive frame sync. frame synchronization for the receiver. fsr is only present on mcbsp2. i/o/z mcbsp1.dr h20 g16 mcbsp receive data. serial receive data input. dr is present on all mcbsps. i mcbsp2.dr p10, aa5 r6, r5 mcbsp receive data. serial receive data input. dr is present on all mcbsps. i mcbsp3.dr aa17, u18 r12, p17 camera interface cam.exclk h19 g13 camera interface external clock. output clock used to provide a timing reference to a camera sensor. o cam.lclk j15 h15 camera interface line clock. input clock to provide external timing reference from camera sensor logic. i cam.vs l18 j17 camera interface vertical sync. vertical synchronization input from external camera sensor. i cam.hs l15 k15 camera interface horizontal sync. horizontal synchronization input from external camera sensor. i cam.d[7:0] j18, j19, j14, k18, k19, k15, k14, l19 g14, g12, h16, j15, g17, h17, h14, j16 camera interface data. data input bus to receive image data from an external camera sensor. i cam.rstz m19 j14 camera interface reset. reset output used to reset or initialize external camera sensor logic. o etm9 trace macro interface etm.clk j15 h15 etm9 trace clock. clock output for standard etm9 test/debug equipment. o etm.sync h19 g13 etm9 trace synchronization. trace sync output for standard etm9 test/debug equipment. o etm.d[7:0] j18, j19, j14, k18, k19, k15, k14, l19 g14, g12, h16, j15, g17, h17, h14, j16 etm9 trace packet data. trace packet outputs for standard etm9 test/debug equipment. o ? i = input, o = output, z = high-impedance ? all core voltage supplies should be tied to the same voltage level (within 0.3 v). during system prototyping phases, it may be useful to maintain a capability for independent measurement of core supply currents to facilitate power optimization experiments. see sections 5.6.1 and 5.6.2 for special v ss considerations with oscillator circuits. introduction 25 august 2002 ? revised august 2003 sprs197b table 2?4. signal description (continued) signal type ? description gdy ball gzg ball etm9 trace macro interface (continued) etm.pstat[2:0] l18, l15, m19 j17, k15, j14 etm9 trace pipe state 2?0. pipeline status outputs for standard etm9 test/debug equipment. o microwire interface uwire.sclk v19, j15 m13, h15 microwire serial clock. this pin drives a clock to a microwire device. the active edge is software configurable. o uwire.sdo w21, h19 p16, g13 microwire serial data out. write data is transferred to a microwire device on this pin. o uwire.sdi u18, j14 p17, h16 microwire serial data in. read data is transferred from a microwire device on this pin. i uwire.cs0 n14, j18 r16, g14 microwire chip select 0. the cs0 output selects a single microwire device (configurable as active high or active low). o uwire.cs3 p15, j19 l12, g12 microwire chip select 3. the cs3 output selects a single microwire device (configurable as active high or active low). o hdq/1-wire interface hdq n20 l16 hdq/1-wire interface. hdq optionally implements one of two serial protocols: hdq or 1-wire. i/o general-purpose i/o (gpio) and mpu i/o (mpuio) gpio15 m20 k16 shared general-purpose i/o. each gpio pin can be used by either the dsp core or the mpu core. control of each gpio pin between the two cores is selected by i/o/z gpio14 n21 k17 shared general-purpose i/o. each gpio pin can be used by either the dsp core or the mpu core. control of each gpio pin between the two cores is selected by the mpu via control registers. each gpio pin may also be configured to cause an i/o/z gpio13 n19 k14 the mpu via control registers. each gpio pin may also be configured to cause an interrupt to its respective core processor. gpio12 n18, w6 l15, p6 interrupt to its respective core processor. gpio5 and gpio10 are not available on the omap5910 device. gpio11 n20, v7 l16, t5 gpio5 and gpio10 are not available on the omap5910 device. gpio9 w8 m8 gpio8 y8 u6 gpio7 m15, y5, v9 l17, n6, r7 gpio6 p19 k13 gpio4 p20 l14 gpio3 p18 k12 gpio2 m14 m15 gpio1 r19 m17 gpio0 r18 m16 ? i = input, o = output, z = high-impedance ? all core voltage supplies should be tied to the same voltage level (within 0.3 v). during system prototyping phases, it may be useful to maintain a capability for independent measurement of core supply currents to facilitate power optimization experiments. see sections 5.6.1 and 5.6.2 for special v ss considerations with oscillator circuits. introduction 26 august 2002 ? revised august 2003 sprs197b table 2?4. signal description (continued) signal type ? description gdy ball gzg ball general-purpose i/o (gpio) and mpu i/o (mpuio) (continued) mpuio12 l19 j16 mpu general-purpose i/o. mpuio pins may only be used by the mpu core. i/o/z mpuio11 w10 r8 mpu general-purpose i/o. mpuio pins may only be used by the mpu core. mpuio8, mpuio9, and mpuio10 are not available on the omap5910 device. i/o/z mpuio7 v10 m9 mpuio8, mpuio9, and mpuio10 are not available on the omap5910 device. mpuio6 w11 r9 mpuio5 t20, w5 l13, u4 mpuio4 t19 n15 mpuio3 v8 p7 mpuio2 n15 n17 mpuio1 u19 m14 mpuio0 y12 n10 pulse-width tone and pulse-width light interface pwt m18 j13 pulse width tone output. the pwt output pin provides a modulated output for use with an external buzzer. o pwl l14 h12 pulse width light output. the pwl output pin provides a pseudo-random modulated voltage output used for lcd or keypad backlighting. o multimedia card/secure digital interface (mmc/sd) mmc.clk v11 u10 mmc/sd clock. clock output to the mmc/sd card. o mmc.cmd/spi.do p11 u8 mmc/sd command / spi data output. mmc/sd commands are transferred to/from this pin. the pin functions as the data output during spi mode. i/o/z mmc.dat3 w11 r9 sd card data bit 3. data bit 3 used in 4-bit secure digital mode. i/o/z mmc.dat2 w10, m15 r8, l17 sd card data bit 2. data bit 2 used in 4-bit secure digital mode. i/o/z mmc.dat1 v10 m9 sd card data bit 1. data bit 1 used in 4 -bit secure digital mode. i/o/z mmc.dat0/spi.di r11 u9 mmc/sd dat0 / spi input. mmc.dat0/spi.di functions as data bit 0 during mmc and secure digital operation. the pin functions as the data input in generic spi mode. i/o/z spi.clk m14 m15 spi clock. spi clock output used during generic spi mode operation. o spi.cs3 p18 k12 spi chip selects. spi chip selects used during generic spi mode operation. o spi.cs2 p20 l14 spi chip selects. spi chip selects used during generic spi mode operation. o spi.cs1 p19 k13 spi.rdy r18 m16 spi ready. spi ready input from spi device used only in generic spi mode operation. i ? i = input, o = output, z = high-impedance ? all core voltage supplies should be tied to the same voltage level (within 0.3 v). during system prototyping phases, it may be useful to maintain a capability for independent measurement of core supply currents to facilitate power optimization experiments. see sections 5.6.1 and 5.6.2 for special v ss considerations with oscillator circuits. introduction 27 august 2002 ? revised august 2003 sprs197b table 2?4. signal description (continued) signal type ? description gdy ball gzg ball universal asynchronous receiver/transmitter interfaces uart1.tx y14 p13 uart transmit. transmit data output. tx is present on all uarts. on uart3, the tx pin implements the txir function during sir mode operation. o uart2.tx v6, m18 r4, j13 uart transmit. transmit data output. tx is present on all uarts. on uart3, the tx pin implements the txir function during sir mode operation. o uart3.tx m18, k18 j13, j15 uart1.rx v14 r11 uart receive. receive data input. rx is present on all uarts. on uart3, the rx pin implements the rxir function during sir mode operation. i uart2.rx r9, l14 m7, h12 uart receive. receive data input. rx is present on all uarts. on uart3, the rx pin implements the rxir function during sir mode operation. i uart3.rx l14, k19 h12, g17 uart1.cts r14 m10 uart clear-to-send. cts is present on all uarts. i uart2.cts y5, l15 n6, k15 uart clear-to-send. cts is present on all uarts. i uart3.cts r13, k15 l10, h17 uart1.rts aa15 u12 uart request-to-send. rts is present on all uarts. on uart3 in irda mode, this pin is sd_mode. o uart2.rts w5, m19 u4, j14 uart request-to-send. rts is present on all uarts. on uart3 in irda mode, this pin is sd_mode. o uart3.rts y13, r19 p11, m17 uart1.dtr w21, y13 p16, p11 uart data-terminal-ready. dtr is only present on uart1 and uart3. o uart3.dtr w21 p16 uart1.dsr u18, r13 p17, l10 uart data-set-ready. dsr is only present on uart1 and uart3. i uart3.dsr u18 p17 uart2.bclk y4 t4 uart baud clock output. a clock of 16x of the uart2 baud rate is driven onto this pin. this feature is only implemented on uart2. o inter-integrated circuit master and slave interface i2c.scl t18 p15 i 2 c serial clock. i2c.scl provides the timing reference for i 2 c transfers. i/o/z i2c.sda v20 n14 i 2 c serial data. i2c.sda provides control and data for i 2 c transfers. i/o/z led pulse generator interface led1 p18 k12 led pulse generator output 1. led1 produces a static or pulsing output used to drive an external led indicator. o led2 t19 n15 led pulse generator output 2. led2 produces a static or pulsing output used to drive an external led indicator. o multichannel serial interfaces (mcsis) mcsi1.clk aa13 u11 mcsi clock. multichannel serial interface clock reference. the clock can be driven in master mode or an external clock may be driven on this signal in slave mode. i/o/z mcsi2.clk y10 t8 mcsi clock. multichannel serial interface clock reference. the clock can be driven in master mode or an external clock may be driven on this signal in slave mode. i/o/z mcsi1.sync v13 t11 mcsi sync. multichannel serial interface frame synchronization signal. the frame sync can be driven in master mode or an external clock may be driven on this signal in slave mode. mcsix.sync may be configured as an active-low or i/o/z mcsi2.sync v9 r7 sync can be driven in master mode or an external clock may be driven on this signal in slave mode. mcsix.sync may be configured as an active-low or active-high sync. ? i = input, o = output, z = high-impedance ? all core voltage supplies should be tied to the same voltage level (within 0.3 v). during system prototyping phases, it may be useful to maintain a capability for independent measurement of core supply currents to facilitate power optimization experiments. see sections 5.6.1 and 5.6.2 for special v ss considerations with oscillator circuits. introduction 28 august 2002 ? revised august 2003 sprs197b table 2?4. signal description (continued) signal type ? description gdy ball gzg ball multichannel serial interfaces (mcsis) (continued) mcsi1.din w13 r10 mcsi data in. multichannel serial interface data input pin. i mcsi2.din aa9 p8 mcsi data in. multichannel serial interface data input pin. i mcsi1.dout w14 n12 mcsi data out. multichannel serial interface data output pin. o mcsi2.dout w9 t7 mcsi data out. multichannel serial interface data output pin. o usb (integrated transceiver interface, can be used with host or function) usb.dp p9 p5 usb internal transceiver d+. the positive side of the integrated usb transceiver?s differential bus. a series resistor of 27 ? (5% tolerance) is required on the usb.dp pin. i/o/z usb.dm r8 p4 usb internal transceiver d?. the negative side of the integrated usb transceiver?s differential bus. a series resistor of 27 ? (5% tolerance) is required on the usb.dm pin. i/o/z usb pin group 1 and 2 (utilizing external transceivers, can be used with host or function) usb1.txen w16 t6 usb transmit enable. driven active (high) when the usb host or function peripheral is driving data onto the usb bus via the txd output. o usb2.txen w9 t7 usb transmit enable. driven active (high) when the usb host or function peripheral is driving data onto the usb bus via the txd output. o usb1.txd w14 n12 usb transmit data. single-ended logic output used to transmit data to the transmit input of an external usb transceiver. usbx.txd may also be used for transceiverless connection between omap5910 and another transceiverless usb o usb2.txd v6 r4 input of an external usb transceiver. usbx.txd may also be used for transceiverless connection between omap5910 and another transceiverless usb device. usb1.vp v13 t11 usb vplus data. single-ended input used to monitor the logical state of the d+ line of the usb bus. usbx.vp should be driven by an external usb transceiver based i usb2.vp aa9 p8 of the usb bus. usbx.vp should be driven by an external usb transceiver based on the state of d+. usb1.vm aa13 u11 usb vminus data. single-ended input used to monitor the logical state of the d? line of the usb bus. usbx.vm should be driven by an external usb transceiver i usb2.vm r9 m7 line of the usb bus. usbx.vm should be driven by an external usb transceiver based on the state of d?. usb1.rcv w13 r10 usb receive data. single-ended logic input used to receive data from the receive output of an external usb transceiver. usbx.rcv may also be used for transceiverless connection between omap5910 and another transceiverless usb i usb2.rcv y5 n6 output of an external usb transceiver. usbx.rcv may also be used for transceiverless connection between omap5910 and another transceiverless usb device. usb1.susp aa17 r12 usb bus segment suspend control. active-high output indicates detection of idle condition on the usb bus for greater than 5 ms. usbx.susp is implemented on o usb2.susp y10 t8 condition on the usb bus for greater than 5 ms. usbx.susp is implemented on both usb ports 1 and 2. usb1.se0 p14 u13 usb single-ended zero. active-high output indicates detection of the single-ended zero state on the usb bus. usbx.se0 is implemented for both usb ports 1 and 2. o usb2.se0 w5 u4 usb single-ended zero. active-high output indicates detection of the single-ended zero state on the usb bus. usbx.se0 is implemented for both usb ports 1 and 2 . o usb1.speed y12 n10 usb 1 bus segment speed control. static control output used by the external transceiver to determine whether usb port 1 is operating in full-speed or low-speed mode. usb1.speed is only implemented on usb port 1. o ? i = input, o = output, z = high-impedance ? all core voltage supplies should be tied to the same voltage level (within 0.3 v). during system prototyping phases, it may be useful to maintain a capability for independent measurement of core supply currents to facilitate power optimization experiments. see sections 5.6.1 and 5.6.2 for special v ss considerations with oscillator circuits. introduction 29 august 2002 ? revised august 2003 sprs197b table 2?4. signal description (continued) signal type ? description gdy ball gzg ball usb miscellaneous signals usb.clko w4 t3 usb clock output. 6-mhz divided clock output of the internal usb dpll provided for reference. common for all usb host and function peripherals. o usb.puen w4 t3 usb pullup enable. control output used in conjunction with an external pullup resistor to implement usb device connect and disconnect via software. usb.puen is used with the usb function peripheral. o usb.vbus r18 m16 usb voltage bus enable. usb.vbus is used to provide a logic-high voltage level which may be used to enable pullup resistors on the usb bus to indicate connection or disconnection status of the omap5910 device as a usb function device. i jtag/emulation interface tck w18 t14 ieee standard 1149.1 test clock. tck is normally a free-running clock signal with a 50% duty cycle. the changes on the test access port (tap) of input signals tdi and tms are clocked into the tap controller, instruction register, or selected test data register on the rising edge of tck. changes at the tap output signal tdo occur on the falling edge of tck. i tdi y19 u17 ieee standard 1149.1 test data input. tdi is clocked into the selected register (instruction or data) on the rising edge of tck. i tdo aa19 u16 ieee standard 1149.1 test data output. the contents of the selected register (instruction or data) are shifted out of tdo on the falling edge of tck. tdo is in the high-impedance state except when the scanning of data is in progress. o tms v17 r13 ieee standard 1149.1 test mode select. this serial control input is clocked into the tap controller on the rising edge of tck. i trst y18 u15 ieee standard 1149.1 test reset. trst , when high, gives the ieee standard 1149.1 scan system control of the operations of the device. if trst is not connected, or driven low, the device operates in its functional mode, and the ieee standard 1149.1 signals are ignored. i emu0 v16 r17 emulation pin 0. when trst is driven high, emu0 is used as an interrupt to or from the emulator system and is defined as input/output by way of the ieee standard 1149.1 scan system. i/o emu1 w17 t13 emulation pin 1. when trst is driven high, emu1 is used as an interrupt to or from the emulator system and is defined as input/output by way of the ieee standard 1149.1 scan system. i/o device clock pins clk32k_in p13 n9 32-khz clock input. digital cmos 32-khz clock input driven by an external 32-khz oscillator if the internal 32-khz oscillator is not used. i clk32k_out y12 n10 32-khz clock output. clock output reflecting the internal 32-khz clock. o clk32k_ctrl aa20 t15 32-khz clock selection control input. clk32k_ctrl selects whether or not the internal 32-khz oscillator is used or if the 32-khz clock is to be provided externally via the clk32k_in input. if clk32k_ctrl is high, the 32-khz internal oscillator is used; if clk32k_ctrl is low, the cmos input clk32k_in is used as a 32-khz clock source. i osc32k_in w12 t10 32-khz crystal xi connection. analog clock input to 32-khz oscillator for use with external crystal. analog osc32k_out r12 t9 32-khz crystal xo connection. analog output from 32-khz oscillator for use with external crystal. analog osc1_in y2 r2 base crystal xi connection. analog input to base oscillator for use with external crystal or to be driven by external 12- or 13-mhz oscillator. analog ? i = input, o = output, z = high-impedance ? all core voltage supplies should be tied to the same voltage level (within 0.3 v). during system prototyping phases, it may be useful to maintain a capability for independent measurement of core supply currents to facilitate power optimization experiments. see sections 5.6.1 and 5.6.2 for special v ss considerations with oscillator circuits. introduction 30 august 2002 ? revised august 2003 sprs197b table 2?4. signal description (continued) signal type ? description gdy ball gzg ball device clock pins (continued) osc1_out w3 p3 base crystal xo connection. analog output from base oscillator for use with external 12- or 13-mhz crystal. analog mclk y9 u7 m-clock. general-purpose clock output which may be configured to run at 12 mhz or 48 mhz. mclk may be configured to drive constantly or only when the mclkreq signal is asserted active high. o bclk y13 p11 b-clock. general purpose clock output which may be configured to run at 12 mhz. bclk may be configured to drive constantly or only when the bclkreq signal is asserted active high. o mclkreq r10 n8 m-clock request. active high request input which allows an external device to request that mclk be driven. i bclkreq r13 l10 b-clock request. active high request input which allows an external device to request that bclk be driven. i reset logic pins pwron_reset g19 f14 reset input to device. active-low asynchronous reset input resets the entire omap5910 device. i mpu_rst v15 p12 mpu reset input. active-low asynchronous reset input resets the mpu core. i rst_out w15 m11 reset output. active-low output is asserted when mpust is active (after synchronization.) o interrupts and miscellaneous control and configuration pins mpu_boot aa17 r12 mpu boot mode. when mpu_boot is low, the mpu boots from chip select 0 of the emifs (flash) interface. when mpu_boot is high, the mpu boots from chip select 3 of emifs. i dma_req_obs l14 h12 dma request external observation output. o irq_obs m18 j13 irq external observation output. o ext_dma_req1 t19 n15 external dma requests. ext_dma_req0 and ext_dma_req1 provide two dma request inputs which external devices may use to trigger system dma transfers. the system dma must be configured in software to respond to these i ext_dma_req0 n15 n17 dma request inputs which external devices may use to trigger system dma transfers. the system dma must be configured in software to respond to these external requests. bfail/ext_fiq w19 r14 battery power failure and external fiq interrupt input. bfail/ext_fiq may be used to gate certain input pins when battery power is low or failing. the pins which may be gated are configured via software. this pin can also optionally be used as an external fiq interrupt source to the mpu. the function of this pin is configurable via software. i ext_master_req r10 n8 external master request. if the 12-mhz clock is provided by an external device instead of using the on-chip oscillator, a high level on this output indicates to the external device that the clock must be driven. a low level indicates that the omap5910 device is in sleep mode and the 12-mhz clock is not necessary. o low_pwr t20 l13 low-power request output. this active-high output indicates that the omap5910 device is in a low-power sleep mode. during reset and functional modes, low_pwr is driven low. this signal can be used to indicate a low-power state to external power management devices in a system or it can be used as a chip select to external sdram memory to minimize current consumption while the sdram is in self-refresh and the omap5910 device is in sleep mode. o conf v18 t16 configuration input. conf selects reserved factory test modes. conf should always be pulled low during device operation. i ? i = input, o = output, z = high-impedance ? all core voltage supplies should be tied to the same voltage level (within 0.3 v). during system prototyping phases, it may be useful to maintain a capability for independent measurement of core supply currents to facilitate power optimization experiments. see sections 5.6.1 and 5.6.2 for special v ss considerations with oscillator circuits. introduction 31 august 2002 ? revised august 2003 sprs197b table 2?4. signal description (continued) signal type ? description gdy ball gzg ball interrupts and miscellaneous control and configuration pins (continued) stat_val/wkup y17 u14 static valid / chip wake-up input. stat_val/wkup may be configured via software to function as an external wake-up signal to the omap5910 device to request chip wake-up during sleep modes. stat_val/wkup is also sampled at reset to select the mmc/sd port. if the mmc/sd peripheral is to be used, this pin must be pulled high during reset. it is recommended that this pin be pulled high during reset regardless of whether or not mmc/sd will be used. i rst_host_out p14 u13 reset host output. a software controllable reset or shutdown output to an external device. o rsvd e5 n11 reserved pin. this pin must be left unconnected. ? power supplies v ss a21, b1, b2, b5, b7, b16, b18, e2, f20, g1, j20, k2, k20, n1, r21, u2, u20, v5, v12, w20, y3, y15, aa1, aa7, aa21 n5, h8, g11, m6, l11, k8, j12, j9, g7, e5, j7, j8, j6, j10, k10, h10, f12, l7, f6, l9, k9, m12, e13, j11, n13 ground. common ground return for all core and i/o voltage supplies. power cv dd ? a9, f2, p12, y20 e8, e2, t17, p10 core supply voltage. supplies power to omap5910 core logic and low-voltage sections of i/o. power cv dd1 ? a3 b3 core supply voltage 1. supplies power to the on-chip shared sram memory (192k-bytes). power cv dd2 ? y1, aa3 k7, l8 core supply voltage 2. supplies power to the mpu subsystem logic and memory. power cv dd3 ? b13, b20, j21, r20 f10, g10, h11, k11 core supply voltage 3. supplies power to the dsp subsystem logic and memory. power cv dd4 ? m2 k2 core supply voltage 4. supplies power to the dpll which provides internal clocks to the core and peripherals (excluding usb peripherals). note: the voltage to this supply pin should be kept as clean as possible to maximize performance. power ? i = input, o = output, z = high-impedance ? all core voltage supplies should be tied to the same voltage level (within 0.3 v). during system prototyping phases, it may be useful to maintain a capability for independent measurement of core supply currents to facilitate power optimization experiments. see sections 5.6.1 and 5.6.2 for special v ss considerations with oscillator circuits. introduction 32 august 2002 ? revised august 2003 sprs197b table 2?4. signal description (continued) signal type ? description gdy ball gzg ball power supplies (continued) cv dda ? y21 r15 analog supply voltage. supplies power to ulpd dpll which provides an internal clock to the usb peripherals. note: the voltage to this supply pin should be kept as clean as possible to maximize performance. power dv dd1 a15, a19, e21, l21, u21, aa11, y16 c12, a14, e14, h13, u21, p9, t12 i/o supply voltage 1. supplies power to the majority of peripheral i/o buffers. dv dd1 may be connected in common with the other dv dd supplies if the same operating voltage is desired. power dv dd2 aa2 u3 i/o supply voltage 2. supplies power to the internal usb transceiver buffers. dv dd2 may optionally be used for usb connect & disconnect detection by connecting dv dd2 to the power from the usb bus in the system. dv dd2 may be connected in common with the other dv dd supplies if the same operating voltage is desired. power dv dd3 y7 n7 i/o supply voltage 3. supplies power to the mcsi2 and mcbsp2 peripheral i/o buffers as well as gpio[9:8] i/o buffers. the dv dd3 supply may operate within a high-voltage or low-voltage range (see section 5.2 for operating conditions). dv dd3 may be connected in common with the other dv dd supplies if the same operating voltage is desired. power dv dd4 a1, a5, a7, b10, b12 d3, d5, a5, d8, e10 i/o supply voltage 4. supplies power to the sdram interface i/o buffers. the dv dd4 supply may operate within a high-voltage or low-voltage range (see section 5.2 for operating conditions). dv dd4 may be connected in common with the other dv dd supplies if the same operating voltage is desired. power dv dd5 c2, e1, h2, l1, p3, r1, v2 h7, d1, f1, k6, l2, l3, u1 i/o supply voltage 5. supplies power to the flash interface i/o buffers. the dv dd5 supply may operate within a high-voltage or low-voltage range (see section 5.2 for operating conditions). dv dd5 may be connected in common with the other dv dd supplies if the same operating voltage is desired. power ? i = input, o = output, z = high-impedance ? all core voltage supplies should be tied to the same voltage level (within 0.3 v). during system prototyping phases, it may be useful to maintain a capability for independent measurement of core supply currents to facilitate power optimization experiments. see sections 5.6.1 and 5.6.2 for special v ss considerations with oscillator circuits. functional overview 33 august 2002 ? revised august 2003 sprs197b 3 functional overview the following functional overview is based on the block diagram in figure 3?1. mpu core (ti925t) (instruction cache, data cache, mmus) system dma controller tms320c55x dsp (instruction cache, saram, daram, dma, h/w accelerators) mpu peripheral bridge lcd i/f mpu interface sram sdram memories flash and sram memories dsp mmu 16 16 32 16 32 32 32 32 32 32 32 16 mpu private peripheral bus dsp public (shared) peripheral bus 32 mpu public peripheral bus 16 dsp dsp public peripherals mcbsp1 mcbsp3 mpu public peripherals mcbsp2 jtag/ emulation i/f osc 12 mhz clock osc omap5910 (289-ball package) etm9 dsp private peripherals timers (3) mpu/dsp shared peripherals mailboxes mpu private peripherals timers (3) 16 memory interface reset external clock mpu bus 32 khz 192k bytes traffic controller (tc) watchdog timer level 1/2 interrupt handlers configuration registers clock/reset/power management watchdog timer level 1/2 interrupt handlers private peripheral bus gpio i/f uart1, uart2, uart3 usb function usb host i c i/f wire i/f camera i/f mpuio 32-khz timer pwt i/f pwl i/f 2 m i f s m i f f i m i f mcsi1 mcsi2 keyboard i/f requests e e mmc/sd lpg x2 rtc etm9 pins are shared with the camera interface. hdq/1?wire i/f fac 32 32 32 local bus i/f and 32 32 ? ? mmu or 13 mhz figure 3?1. omap5910 functional block diagram functional overview 34 august 2002 ? revised august 2003 sprs197b 3.1 functional block diagram features the omap5910 device includes the following functional blocks: ? arm9tdmi-based mpu core ? 16k-byte instruction cache and 8k-byte data cache ? memory management units (mmus) for instruction and data ? two 64-entry translation look-aside buffers (tlbs) for mmus ? 17-word write buffer ? c55x dsp subsystem ? 48k-word single-access ram (saram) (96k bytes) ? 32k-word dual-access ram (daram) (64k bytes) ? 16k-word rom (32k bytes) ? 24k-byte instruction cache ? six-channel dma controller ? hardware accelerators for dct, idct, pixel interpolation, and motion estimation ? nine-channel system dma controller ? traffic controller providing shared access to three memory interfaces: ? emiff external memory interface providing 16-bit interface to 64m bytes of standard sdram ? emifs external memory interface providing 16-bit interface to 128m bytes of flash, rom, or asynchronous memories ? internal memory interface (imif) providing 32-bit interface to 192k bytes of internal sram ? dsp memory management unit (mmu) configured by the mpu ? mpu interface (mpui) allowing mpu and system dma to access dsp subsystem memory and dsp public peripherals ? local bus interface (with mmu) allowing usb host peripheral direct access to system memories. ? dsp private peripherals (accessible only by the dsp) ? three 32-bit general-purpose timers ? watchdog timer ? level 1/level 2 interrupt handlers ? dsp public peripherals (accessible by the dsp, dsp dma, and the mpu via the mpu interface) ? two multichannel buffered serial ports (mcbsps) ? two multichannel serial interfaces (mcsis) ideal for voice data ? mpu private peripherals (accessible only by the mpu) ? three 32-bit general-purpose timers ? watchdog timer ? level 1/level 2 interrupt handlers ? configuration registers for pin-multiplexing and other device-level configurations ? lcd controller supporting monochrome panels or stn and tft color panels functional overview 35 august 2002 ? revised august 2003 sprs197b ? mpu public peripherals (accessible by the mpu and the system dma) ? multichannel buffered serial port (mcbsp) ? usb function interface (optional internal transceiver shared with usb host interface) ? usb host interface with up to three ports (optional internal transceiver shared with usb function interface) ? one integrated usb transceiver for either host or function ? inter-integrated circuit (i 2 c) multi-mode master and slave interface ? microwire serial interface ? camera interface providing connectivity to cmos image sensors ? up to ten mpu general-purpose i/os (mpuios) ? 32-khz timer for use with mpu os ? pulse-width tone (pwt) module for tone generation ? pulse-width light (pwl) module for lcd backlight control ? keyboard interface (6 x 5 or 8 x 8 matrix) ? multimedia card or secure digital interface (mmc/sd) ? also configurable as generic spi port ? two led pulse generator modules (lpg) ? real-time clock module (rtc) ? hdq or 1-wire master interface for serial communication to battery management devices ? frame adjustment counter (fac) ? mpu/dsp shared peripherals (controlling processor is selected by the mpu) ? four mailboxes for interprocessor communications ? up to 14 general-purpose i/o pins with interrupt capability to either processor ? three uarts (uart3 has sir mode for irda functionality) ? clock/reset/power management modules ? configurable digital phase-locked loop (dpll) providing clocks to mpu, dsp, and tc ? dedicated usb dpll providing clocking to usb modules ? integrated base (12- or 13-mhz) and 32-khz oscillators utilizing external crystals ? reset, clocking and idle/sleep controls for power management ? jtag and etm9 interfaces for emulation and debug functional overview 36 august 2002 ? revised august 2003 sprs197b 3.2 mpu memory maps 3.2.1 mpu global memory map the mpu has a unified address space. therefore, the internal and external memories for program and data as well as peripheral registers and configuration registers are all accessed within the same address space. the mpu space is always addressed using byte addressing. table 3?1 provides a high level illustration of the entire mpu addressable space. further detail regarding the peripheral and configuration registers is provided in sections 3.2.2, 3.15, and 3.17. table 3?1. omap5910 mpu global memory map byte address range on-chip external interface 0x0000 0000 ? 0x01ff ffff emifs (flash cs0) 32m bytes 0x0200 0000 ? 0x03ff ffff reserved 0x0400 0000 ? 0x05ff ffff emifs (flash cs1) 32m bytes 0x0600 0000 ? 0x07ff ffff reserved 0x0800 0000 ? 0x09ff ffff emifs (flash cs2) 32m bytes 0x0a00 0000 ? 0x0bff ffff reserved 0x0c00 0000 ? 0x0dff ffff emifs (flash cs3) 32m bytes 0x0e00 0000 ? 0x0fff ffff reserved 0x1000 0000 ? 0x13ff ffff emiff (sdram) 64m bytes 0x1400 0000 ? 0x1fff ffff reserved 0x2000 0000 ? 0x2002 ffff imif internal sram 192k bytes 0x2003 0000 ? 0x2fff ffff reserved 0x3000 0000 ? 0x5fff ffff local bus space for usb host 0x6000 0000 ? 0xdfff ffff reserved 0xe000 0000 ? 0xe0ff ffff dsp public memory space (accessible via mpui) 16m bytes 0xe100 0000 ? 0xefff ffff dsp public peripherals (accessible via mpui) 0xf000 0000 ? 0xfffa ffff reserved 0xfffb 0000 ? 0xfffb ffff mpu public peripherals ? 0xfffc 0000 ? 0xfffc ffff mpu/dsp shared peripherals 0xfffd 0000 ? 0xfffe ffff mpu private peripherals 0xffff 0000 ? 0xffff ffff reserved ? some peripherals within this memory region are actually shared peripherals (uart 1,2,3). functional overview 37 august 2002 ? revised august 2003 sprs197b 3.2.2 mpu subsystem registers memory map the mpu accesses peripheral and configuration registers in the same way that internal and external memory is accessed. the following tables specify the mpu base addresses where each set of registers is accessed. all accesses to these registers must utilize the appropriate access width (8-, 16-, or 32-bit-wide accesses) as indicated in the tables. accessing registers with the incorrect access width may result in unexpected results including a ti peripheral bus (tipb) bus error and associated tipb interrupt. refer to sections 3.15, 3.16, and 3.17 for more detail about each of these register sets including individual register addresses, register names, descriptions, supported access types (read, write or read/write) and reset values. table 3?2. mpu private peripheral registers mpu base address register set access width 0xfffe 0000 mpu level 2 interrupt handler registers 32 0xfffe c000 lcd controller registers 32 0xfffe c500 mpu timer1 registers 32 0xfffe c600 mpu timer2 registers 32 0xfffe c700 mpu timer3 registers 32 0xfffe c800 mpu watchdog timer registers 32 0xfffe cb00 mpu level 1 interrupt handler registers 32 0xfffe d800 system dma controller registers 16 table 3?3. mpu public peripheral registers mpu base address register set access width 0xfffb 1000 mcbsp2 registers 16 0xfffb 3000 microwire registers 16 0xfffb 3800 i 2 c registers 16 0xfffb 4000 usb function registers 16 0xfffb 4800 rtc registers 8 0xfffb 5000 mpuio/keyboard registers 16 0xfffb 5800 pulse width light (pwl) registers 8 0xfffb 6000 pulse width tone (pwt) registers 8 0xfffb 6800 camera interface registers 32 0xfffb 7800 mmc/sd registers 16 0xfffb 9000 timer 32k registers 32 0xfffb a000 usb host registers 32 0xfffb a800 frame adjustment counter (fac) registers 16 0xfffb c000 hdq/1-wire registers 8 0xfffb d000 led pulse generator 1 (lpg1) registers 8 0xfffb d800 led pulse generator 2 (lpg2) registers 8 table 3?4. mpu/dsp shared peripheral registers mpu base address register set access width 0xfffb 0000 uart1 registers 8 0xfffb 0800 uart2 registers 8 0xfffb 9800 uart3 registers 8 0xfffc e000 gpio interface registers 16 0xfffc f000 mailbox registers 16 functional overview 38 august 2002 ? revised august 2003 sprs197b table 3?5. dsp public peripheral registers (accessible via mpui port) mpu base address register set access width 0xe101 1800 mcbsp1 registers 16 0xe101 2000 mcsi2 registers 16 0xe101 2800 mcsi1 registers 16 0xe101 7000 mcbsp3 registers 16 table 3?6. mpu configuration registers mpu base address register set access width 0xfffb c800 mpu uart tipb bus switch registers 16 0xfffe 0800 ultra low-power device (ulpd) registers 16 0xfffe 1000 omap5910 configuration registers 32 0xfffe 1800 device die identification registers 32 0xfffe c100 local bus control registers 32 0xfffe c200 local bus mmu registers 32 0xfffe c900 mpu interface (mpui) registers 32 0xfffe ca00 tipb (private) bridge 1 config registers 32 0xfffe cc00 traffic controller registers 32 0xfffe ce00 mpu clock/reset/power control registers 32 0xfffe cf00 dpll1 configuration registers 32 0xfffe d200 dsp mmu registers 32 0xfffe d300 tipb (public) bridge 2 config registers 16 0xfffe d400 jtag identification registers 32 3.3 dsp memory maps the dsp supports a unified program/data memory map (program and data accesses are made to the same physical space), however peripheral registers are located in a separate i/o space which is accessed via the dsp?s port instructions. 3.3.1 dsp global memory map the dsp subsystem contains 160k bytes of on-chip sram (64k bytes of daram and 96k bytes of saram). the mpu also has access to these memories via the mpui (mpu interface) port. the dsp also has access to the shared system sram (192k bytes) and both emif spaces (emiff and emifs) via the dsp memory management unit (mmu) which is configured by the mpu. table 3?7 shows the high-level program/data memory map for the dsp subsystem. dsp data accesses utilize 16-bit word addresses while dsp program fetches utilize byte addressing. table 3?7. dsp global memory map byte address range word address range internal memory external memory ? 0x00 0000 ? 0x00 ffff 0x00 0000 ? 0x00 7fff daram 64k bytes 0x01 0000 ? 0x02 7fff 0x00 8000 ? 0x01 3fff saram 96k bytes 0x02 8000 ? 0x04 ffff 0x01 4000 ? 0x02 7fff reserved 0x05 0000 ? 0xff 7fff 0x02 8000 ? 0x7f bfff managed by dsp mmu 0xff 8000 ? 0xff ffff 0x7f c000 ? 0x7f ffff pdrom (mpnmc = 0) managed by dsp mmu (mpnmc =1) ? this space could be external memory or internal shared system memory depending on the dsp mmu configuration. functional overview 39 august 2002 ? revised august 2003 sprs197b 3.3.2 on-chip dual-access ram (daram) the daram is located in the byte address range 000000h?00ffffh and is composed of eight blocks of 8k bytes each (see table 3?8). each daram block can perform two accesses per cycle (two reads, two writes, or a read and a write). table 3?8. daram blocks byte address range word address range memory block 0x00 0000 ? 0x00 1fff 0x00 0000 ? 0x00 0fff daram 0 0x00 2000 ? 0x00 3fff 0x00 1000 ? 0x001fff daram 1 0x00 4000 ? 0x00 5fff 0x00 2000 ? 0x00 2fff daram 2 0x00 6000 ? 0x00 7fff 0x00 3000 ? 0x00 3fff daram 3 0x00 8000 ? 0x00 9fff 0x00 4000 ? 0x00 4fff daram 4 0x00 a000 ? 0x00 bfff 0x00 5000 ? 0x00 5fff daram 5 0x00 c000 ? 0x00 dfff 0x00 6000 ? 0x00 6fff daram 6 0x00 e000 ? 0x00 ffff 0x00 7000 ? 0x00 7fff daram 7 3.3.3 on-chip single-access ram (saram) the saram is located at the byte address range 010000h?03ffffh and is composed of 12 blocks of 8k bytes each (see table 3?9). each saram block can perform one access per cycle (one read or one write). table 3?9. saram blocks byte address range word address range memory block 0x01 0000 ? 0x01 1fff 0x00 8000 ? 0x00 8fff saram 0 0x01 2000 ? 0x01 3fff 0x00 9000 ? 0x00 9fff saram 1 0x01 4000 ? 0x01 5fff 0x00 a000 ? 0x00 afff saram 2 0x01 6000 ? 0x01 7fff 0x00 b000 ? 0x00 bfff saram 3 0x01 8000 ? 0x01 9fff 0x00 c000 ? 0x00 cfff saram 4 0x01 a000 ? 0x01 bfff 0x00 d000 ? 0x00 dfff saram 5 0x01 c000 ? 0x01 dfff 0x00 e000 ? 0x00 efff saram 6 0x01 e000 ? 0x01 ffff 0x00 f000 ? 0x00 ffff saram 7 0x02 0000 ? 0x02 1fff 0x01 0000 ? 0x01 0fff saram 8 0x02 2000 ? 0x02 3fff 0x01 1000 ? 0x01 1fff saram 9 0x02 4000 ? 0x02 5fff 0x01 2000 ? 0x01 2fff saram 10 0x02 6000 ? 0x02 7fff 0x01 3000 ? 0x01 3fff saram 11 functional overview 40 august 2002 ? revised august 2003 sprs197b 3.3.4 dsp i/o space memory map the dsp i/o space is a separate address space from the data/program memory space. the i/o space is accessed via the dsp?s port instructions. the public and shared peripheral registers are also accessible by the mpu through the mpui (mpu interface) port. the dsp i/o space is accessed using 16-bit word addresses. the following tables specify the dsp base addresses where each set of registers is accessed. all accesses to these registers must utilize the appropriate access width as indicated in the tables. accessing registers with the incorrect access width may cause unexpected results including a ti peripheral bus (tipb) bus error and associated tipb interrupt. refer to sections 3.16 and 3.17 for more detail about each of these register sets including individual register addresses, register names, descriptions, supported access types (read, write or read/write) and reset values. table 3?10. dsp private peripheral registers dsp base address register set access width 0x00 0c00 dsp dma controller registers 16 0x00 2800 dsp timer1 registers 16 0x00 2c00 dsp timer2 registers 16 0x00 3000 dsp timer3 registers 16 0x00 3400 dsp watchdog timer registers 16 0x00 3800 dsp interrupt interface registers 16 0x00 4800 level2 interrupt handler registers 16 table 3?11. dsp public peripheral registers dsp base address register set access width 0x00 8c00 mcbsp1 registers 16 0x00 9000 mcsi2 registers 16 0x00 9400 mcsi1 registers 16 0x00 b800 mcbsp3 registers 16 table 3?12. dsp/mpu shared peripheral registers dsp base address register set access width 0x00 8000 uart1 registers 8 0x00 8400 uart2 registers 8 0x00 cc00 uart3 registers 8 0x00 f000 gpio interface registers 16 0x00 f800 mailbox registers 16 table 3?13. dsp configuration registers dsp base address register set access width 0x00 0000 dsp tipb bridge config registers 16 0x00 0800 dsp emif config registers 16 0x00 1400 dsp i-cache registers 16 0x00 4000 dsp clock mode registers 16 0x00 e400 dsp uart tipb bus switch registers 16 functional overview 41 august 2002 ? revised august 2003 sprs197b 3.4 dsp external memory (managed by mmu) when the dsp mmu is off, the 24 address lines are directly copied to the traffic controller without any modification. there is no virtual-to-physical address translation. all the addresses between 0x05 0000 and 0x00ff f800 (0x00ff ffff if dsp bit mp/mc = 1) are redirected to the first sector of flash (cs0) in the shared memory space (shared by mpu and dsp). internal ram rom (flash cs1) 0x0000 0000 0x0400 0000 0x0800 0000 0x0c00 0000 0x1000 0000 0x2000 0000 0x05 0000 0x00 0000 byte address 0xff 8000 0xff ffff dsp memory shared memory 0x01ff ffff 0x05ff ffff 0x09ff ffff 0x0dff ffff 0x13ff ffff reserved 0x2002 ffff byte address reserved reserved reserved reserved (flash cs0) emifs emifs emifs emifs emiff imif (flash cs2) (sdram) (flash cs3) (internal sram) figure 3?2. dsp mmu off functional overview 42 august 2002 ? revised august 2003 sprs197b when the dsp mmu is on, the 24 address lines (virtual address) are relocated within a physical 32-bit address by the dsp mmu. the dsp mmu is controlled by the mpu. internal ram rom flash cs0 (flash cs1) (flash cs2) (flash cs3) (sdram) (internal sram) 0x05 0000 0x00 0000 byte address 0xff 8000 0xff ffff dsp memory shared memory 0x0000 0000 0x0400 0000 0x0800 0000 0x0c00 0000 0x1000 0000 0x2000 0000 0x01ff ffff 0x05ff ffff 0x09ff ffff 0x0dff ffff 0x13ff ffff 0x2002 ffff byte address reserved reserved reserved reserved reserved (flash cs0) emifs emifs emifs emifs emiff imif figure 3?3. dsp mmu on functional overview 43 august 2002 ? revised august 2003 sprs197b 3.5 mpu and dsp private peripherals the mpu and dsp each have their own separate private peripheral bus. peripherals on each of these private buses may only be accessed by their respective processors. for instance, the dsp timers on the dsp private peripheral bus are not accessible by the mpu or the system dma controller. 3.5.1 timers the mpu and dsp each have their own three 32-bit timers available on their respective private ti peripheral bus (tipb). these timers are used by the operating systems to provide general-purpose housekeeping functions, or in the case of the dsp, to also provide synchronization of real-time processing functions. these timers may be configured either in auto-reload or one-shot mode with on-the-fly read capability. the timers generate an interrupt to the respective processor (mpu or dsp) when the timer?s down-counter is equal to zero. 3.5.2 32k timer (mpu only) the mpu has one 32k timer that runs on the 32-khz clock as opposed to the mpu subsystem domain clock. the mpu subsystem operating system (os) requires interrupts at regular time intervals for os scheduling purpose (typically 1 ms to 30 ms). these time intervals can be generated using the mpu?s three 32-bit general-purpose timers. however, these timers cannot be used in sleep modes when the system clock is not operating. therefore, a 32-khz clock-based timer is needed to provide the required os timing interval. 3.5.3 watchdog timer the mpu and dsp each have a single watchdog timer. each watchdog timer can be configured as either a watchdog timer or a general-purpose timer. a watchdog timer requires that the mpu or dsp software or os periodically write to the appropriate wdt count register before the counter underflows. if the counter underflows, the wdt generates a reset to the appropriate processor (mpu or dsp). the dsp wdt resets only the dsp processor while the mpu wdt resets both processors (mpu and dsp). the watchdog timers are useful for detecting user programs that are stuck in an infinite loop, resulting in loss of program control or in a runaway condition. when used as a general-purpose timer, the wdt is a 16-bit timer configurable either in autoreload or one-shot mode with on-the-fly read capability. the timer generates an interrupt to the respective processor (mpu or dsp) when the timer?s down-counter is equal to zero. 3.5.4 interrupt handlers the mpu and dsp each have two levels of interrupt handling, allowing up to 39 interrupts to the dsp and 63 interrupts to the mpu. 3.5.5 lcd controller the omap5910 device includes an lcd controller that interfaces with most industry-standard lcds. the lcd controller is configured by the mpu and utilizes a dedicated channel on the system dma to transfer data from the frame buffer. the frame buffer can be implemented using the internal shared sram (192k bytes) or optionally using external sdram via the emiff. using the frame buffer as its data source, the system dma must provide data to the fifo at the front end of the lcd controller data path at a rate sufficient to support the chosen display mode and resolution. optimal performance is achieved when using the internal sram as the frame buffer. the panel size is programmable, and can be any width (line length) from 16 to 1024 pixels in 16-pixel increments. the number of lines is set by programming the total number of pixels in the lcd. the total frame size is programmable up to 1024 x 1024. however, frame sizes and frame rates supported in specific applications will depend upon the available memory bandwidth allowed by the specific application as well as the maximum configurable pixel clock rate. functional overview 44 august 2002 ? revised august 2003 sprs197b the screen is intended to be mapped to the frame buffer as one contiguous block where each horizontal line of pixels is mapped to a set of consecutive bytes of words in the frame memory. the principle features of the lcd controller are: ? dedicated 64-entry x 16-bit fifo ? dedicated lcd dma channel for lcd ? programmable display including support for 2-, 4-, 8-, 12-, and 16-bit graphics modes ? programmable display resolutions up to 1024 pixels by 1024 lines (assuming suf ficient system bandwidth) ? support for passive monochrome (stn) displays ? support for passive color (stn) displays ? support for active color (tft) displays ? patented dithering algorithm, providing: ? 15 grayscale levels for monochrome passive displays ? 3375 colors for color passive displays ? 65536 colors for active color displays ? 256-entry x 12-bit palette ? programmable pixel rate ? pixel clock plus horizontal and vertical synchronization signals ? ac-bias drive signal ? active display enable signal ? 256-entry x 12-bit palette ? dual-frame buffers 3.6 mpu public peripherals peripherals on the mpu public peripheral bus may only be accessed by the mpu and the system dma controller, which is configured by the mpu. this bus is called a public bus because it is accessible by the system dma controller. the dsp cannot access peripherals on this bus. 3.6.1 usb host controller the omap5910 usb host controller communicates with usb devices at the usb low-speed (1.5m-bit/s maximum) and full-speed (12m-bit/s maximum) data rates. the controller is usb compliant. for additional information, see the universal serial bus specification, revision 2.0 and the openhci ? open host controller interface specification for usb, release 1.0a , hereafter called the ohci specification for usb. the omap5910 usb host controller implements the register set and makes use of the memory data structures which are defined in the ohci specification for usb. these registers and data structures are the mechanism by which a usb host controller driver software package may control the omap5910 usb host controller. the usb host controller is connected to the mpu public peripheral bus for mpu access to registers. the usb host controller gains access to the data structures in system memory via the internal local bus interface. the omap5910 device implements a variety of signal multiplexing options that allows use of the usb host controller with any of the three available usb interfaces on the device. one of these interfaces utilizes an integrated usb transceiver, while the other two require external transceivers. the host controller can support up to three downstream ports. the omap5910 usb host controller implementation does not implement every aspect of the functionality defined in the ohci specification for usb. the differences focus on power switching, overcurrent reporting, and the ohci ownership change interrupt. other restrictions are imposed by omap5910 system memory addressing mechanisms and the effects of the omap5910 pin-multiplexing options. functional overview 45 august 2002 ? revised august 2003 sprs197b 3.6.2 usb function peripheral the usb function peripheral provides a full-speed function interface between the mpu and the usb wire. the module handles usb transactions with minimal mpu intervention and is fully compliant to usb standard. the usb function module supports one control endpoint (ep0), up to 15 in endpoints, and up to 15 out endpoints. the exact endpoint configuration is software-programmable. the specific items of a configuration for each endpoint are: the size in bytes, the direction (in, out), the type (bulk/interrupt or isochronous), and the associated endpoint number. the usb function module also supports the use of three system dma channels for in endpoints and three system dma channels for out endpoints for either bulk/interrupt or isochronous transactions. the omap5910 device implements a variety of signal-multiplexing options that allow use of the usb function peripheral with any one of the three available usb interfaces on the device. one of these interfaces utilizes an integrated usb transceiver, while the other two require external transceivers. the usb function can only utilize one of these ports at a time. the other ports may be used simultaneously by the usb host controller peripheral. 3.6.3 multichannel buffered serial port (mcbsp) the multichannel buffered serial port (mcbsp) provides a high-speed, full-duplex serial port that allow direct interface to audio codecs, and various other system devices. the mpu public peripheral bus has access to one mcbsp, which is mcbsp2. the mcbsp provides: ? full-duplex communication ? double-buffer data registers, which allow a continuous data stream ? independent framing and clocking for receive and transmit in addition, the mcbsp has the following capabilities: ? direct interface to: ? t1/e1 framers ? mvip switching-compatible and st-bus compliant devices ? iom-2 compliant device ? ac97-compliant device ? i2s-compliant device ? serial peripheral interface (spi) ? multichannel transmit and receive of up to 128 channels ? a wide selection of data sizes, including: 8, 12, 16, 20, 24, or 32 bits ? -law and a-law companding ? programmable polarity for both frame synchronization and data clocks ? programmable internal clock and frame generation note: all of the standard mcbsp pins are not necessarily available on every mcbsp on the omap5910 device. in the case of the mpu?s mcbsp2, the following pins are available: ? clkx and clkr (transmit and receive clocks) ? fsx and fsr (transmit and receive frame syncs) ? dx and rx (transmit and receive data) the functional clock to the mcbsp2 peripheral is configurable to the dpll clock rate with a divider of 1, 2, 4, or 8. mcbsp2 does not have a clks external clock reference pin. therefore, if the mcbsp2 sample rate generator (srg) is used, the only reference clock available to the sample rate generator is a programmable clock from the mpu domain. functional overview 46 august 2002 ? revised august 2003 sprs197b 3.6.4 i 2 c master/slave interface the i 2 c master/slave interface is compliant to philips i 2 c-bus specification version 2.1 master bus. the i 2 c controller supports the multimaster mode, which allows more than one device capable of controlling the bus to be connected to it. including the omap5910 device, each i 2 c device is recognized by a unique address and can operate as either transmitter or receiver, depending on the function of the device. in addition to being a transmitter or receiver, a device connected to the i 2 c bus ? can also be considered as master or slave when performing data transfers. the i 2 c interface supports the following features: ? compliant to philips i 2 c-bus specification version 2.1 ? support standard mode (up to 100k bits/s) and fast mode (up to 400k bits/s) ? 7-bit and 10-bit device addressing modes ? general call ? start/restart/stop ? multimaster transmitter/slave receiver mode ? multimaster receiver/slave transmitter mode ? combined master transmit/receive and receive/transmit mode ? built-in fifo for buffered read or write ? module enable/disable capability ? programmable clock generation ? supports use of two dma channels the i 2 c interface does not support the following features: ? high-speed (hs) mode for transfer rates up to 3.4m bits ? c-bus compatibility mode 3.6.5 microwire serial interface the microwire interface is a serial synchronous interface that can drive up to four serial external components. the interface is compatible with the microwire standard and is seen as the master. microwire is typically used to transmit control and status information to external peripheral devices or to transmit data to or from small nonvolatile memories such as serial eeproms or serial flash devices. 3.6.6 multimedia card/secure digital (mmc/sd) interface the mmc/sd interface controller provides an interface to mmc or sd memory cards plus up to three serial spi flash cards or other spi devices. the controller handles mmc/sd or spi transactions with minimal mpu intervention, allowing optional use of two system dma channels for transfer of data. the following combination of external devices is supported: ? one or more mmc memory cards sharing the same bus plus up to three devices with 8-bit spi protocol interface (serial flash memories, etc.). ? one single sd memory card plus up to three devices with 8-bit spi protocol interface. note: other combinations such as two sd cards or one mmc card with one sd card are not supported. the mpu software must manage transaction semantics, while the mmc/sd controller deals with mmc/sd protocol at the transmission level: packing data, adding the crc, generating the start/end bit and checking for syntactical correctness. sd mode wide bus width is also supported. when interfacing with 8-bit spi devices, the mmc/sd module does not perform any mmc specific function, rather it provides a generic spi interface. several additional interface pins are utilized to provide the spi clock and spi chip selects. i 2 c bus is a trademark of philips electronics n.v. functional overview 47 august 2002 ? revised august 2003 sprs197b 3.6.7 hdq/1-wire interface this module allows implementation of both hdq and the 1-wire protocols. these protocols use a single wire to communicate between a master and a slave. the hdq/1-wire pin is open-drain and requires an external pullup resistor. hdq and 1-wire interfaces can be found on commercially available battery management and power management devices. the interface can be used to send command and status information between omap5910 and such a battery or power management device. 3.6.8 camera interface the camera interface is an 8-bit external port which may be used to accept data from an external camera sensor. the interface handles multiple image formats synchronized on vertical and horizontal synchronization signals. data transfer to the camera interface may be done synchronously or asynchronously. the camera interface module converts the 8-bit data transfers into 32-bit words and utilizes a 128-word buffer to facilitate efficient data transfer to memory. data may be transferred from the camera interface buffer to internal memory by the system dma controller or directly by the mpu. the interface may utilize an externally driven clock at rates up to 13 mhz or may optionally provide an output reference clock at rates of 8 mhz, 9.6 mhz, or 24 mhz when the camera interface is configured for clocking from the internal 48 mhz. when the camera interface is configured to obtain clocking from the base oscillator frequency (12 mhz or 13 mhz), the camera interface clock is configurable to operate at the base frequency or one half the base frequency (6 mhz or 6.5 mhz). 3.6.9 mpuio/keyboard interface the mpuio pins may be used as either general-purpose i/o for the mpu or as a keyboard interface to a 6 x 5 or 8 x 8 keypad array. if a 6 x 5 keypad array is implemented, the unused mpuio pins may be used as gpio. when used as gpio, each pin may be configured individually as either an output or an input, and they may be individually configured to generate mpu interrupts based on a level change (falling or rising) after a debouncing process. these mpuio interrupts may be used to wake up the device from deep-sleep mode using the 32-khz clock. the mpuio pins may also be used as a keyboard interface. the keyboard interface provides the following pins: ? kb.r[7:0] input pins for row lines ? kb.c[7:0] output pins for column lines to allow key-press detection, all input pins (kb.rx) are pulled up to dv dd and all output pins (kb.cx) are driven low level. the kb.r[7:0] and kb.c[7:0] pins should be connected to an external keyboard matrix such that when a key on the matrix is pressed, the corresponding row and column lines are shorted together. any action on a key generates an interrupt to the mpu, which then scans the column lines in a particular sequence to determine which key or keys have been pressed. 3.6.10 pulse-width light (pwl) the pulse-width light (pwl) module provides control of the lcd or keypad backlighting by employing a random sequence generator. this voltage-level control technique decreases the spectral power at the modulator harmonic frequencies. the module uses a switchable 32-khz clock. 3.6.11 pulse-width tone (pwt) the pulse-width tone (pwt) module generates a modulated frequency signal for use with an external buzzer. the frequency is programmable between 349 hz and 5276 hz with 12 half-tone frequencies per octave. the volume level of the output is also programmable. functional overview 48 august 2002 ? revised august 2003 sprs197b 3.6.12 led pulse generator there are two separate led pulse generator (lpg) modules. each lpg module provides an output for an indication led. the blinking period is programmable between 152 ms and 4 s or the led can be switched on or off permanently. 3.6.13 real-time clock the real-time clock (rtc) module provides an embedded rtc for use in applications which need to track real time. this peripheral is not an ultra-low-power module?meaning that the rtc module cannot be powered independently without powering the omap5910 mpu core. therefore, if an ultra-low-power rtc is desired for a system application, an external rtc should be used. the rtc module has the following features: ? time information (seconds/minutes/hours) directly in bcd code ? calendar information (day/month/year/day of the week) directly in bcd code up to year 2099 ? interrupts generation, periodically (1s/1m/1h/1d period) or at a precise time of the day (alarm function) ? 30-s time correction ? oscillator frequency calibration 3.6.14 frame adjustment counter the frame adjustment counter (fac) is a simple peripheral that counts the number of rising edges of one signal (start of frame interrupt of the usb function) during a programmable number of rising edges of a second signal (transmit frame synchronization of mcbsp2). the fac may only be used with these specific usb function and mcbsp2 signals. the count value can be used by system-level software to adjust the duration of the two time domains with respect to each other to reduce overflow and underflow. if the data being transferred is audio data, this module can be part of a solution that reduces pops and clicks. the fac module generates one second-level interrupt to the mpu. 3.7 dsp public peripherals peripherals on the dsp public peripheral bus are directly accessible by the dsp and dsp dma. these peripherals may also be accessed by the mpu and system dma controller via the mpui interface. the mpui interface must be properly configured to allow this access. 3.7.1 multichannel buffered serial port (mcbsp) the multichannel buffered serial port (mcbsp) provides a high-speed, full-duplex serial port that allow direct interface to audio codecs and various other system devices. refer to section 3.6.3 for a list of features provided by the mcbsp. the dsp public peripheral bus has access to two mcbsps: mcbsp1 and mcbsp3. note: all of the standard mcbsp pins are not necessarily available on every mcbsp on the omap5910 device. in the case of the two dsp mcbsps, the following pins are available: ? mcbsp1 pins: ? clkx (transmit clock) ? fsx (transmit frame sync) ? dx and dr (transmit and receive data) ? clks (external reference to sample rate generator) ? mcbsp3 pins: ? clkx (transmit clock) ? fsx (transmit frame sync) ? dx and dr (transmit and receive data) functional overview 49 august 2002 ? revised august 2003 sprs197b because mcbsp1 and mcbsp3 do not have the clkr and fsr pins available, the transmit clock and frame sync pins (clkx and fsx) must be used for bit clock and frame synchronization on both the transmit and receive channels of these mcbsps. the functional clock to mcbsp1 and mcbsp3 is fixed at the omap5910 base operating frequency (12 mhz or 13 mhz). the bit-clock rate for these mcbsps is therefore limited to 6 or 6.5 mhz (one half the base frequency). only mcbsp1 has the clks pin available. if the sample rate generator (srg) is used on mcbsp1, the reference clock to the srg can be configured to be either an external reference provided on the clks pin, or the internal base (12- or 13-mhz) device clock. however, if the srg is used on mcbsp3, the only reference clock available to this srg is the base device clock as clock reference. 3.7.2 multichannel serial interface (mcsi) the multichannel serial interface (mcsi) provides flexible serial interface with multichannel transmission capability. the mcsi allows the dsp to access a variety of external devices, such as audio codecs and other types of analog converters. the dsp public peripheral bus has access to two mcsis: mcsi1 and mcsi2. these mcsis provide full-duplex transmission and master or slave clock control. all transmission parameters are configurable to cover the maximum number of operating conditions. the mcsis have the following features: ? master or slave clock control (transmission clock and frame synchronization pulse) ? programmable transmission clock frequency (master mode) up to one half the omap5910 base frequency (12 or 13 mhz) ? reception clock frequency (slave mode) of up to the base frequency (12 or 13 mhz) ? single-channel or multichannel (x16) frame structure ? programmable word length: 3 to 16 bits ? full-duplex transmission ? programmable frame configuration ? continuous or burst transmission ? normal or alternate framing ? normal or inverted frame and clock polarities ? short or long frame pulse ? programmable oversize frame length ? programmable frame length ? programmable interrupt occurrence time (tx and rx) ? error detection with interrupt generation on wrong frame length ? system dma support for both tx and rx data transfers 3.8 shared peripherals the shared peripherals are connected to both the mpu public peripheral bus and the dsp public peripheral bus. in the case of the uarts, these connections are achieved via a ti peripheral bus switch, which must be configured to allow mpu or dsp access to the uarts. the other shared peripherals have permanent connections to both public peripheral buses, although read and write accesses to each peripheral register may differ. 3.8.1 universal asynchronous receiver/transmitter (uart) the omap5910 device has three universal asynchronous receiver/transmitter (uart) peripherals which are accessible on the dsp public and mpu public peripheral buses. a ti peripheral bus switch configured by the mpu allows either tipb access to these uart peripherals. all three uarts are standard 16c750-compatible uarts implementing an asynch ronous transfer protocol with various flow control options. two of the three uarts (uart1 and uar t2) have autobaud capability to automatically determine and adjust to the baud rate of the external connected device. one of the uarts (uart3) can function as a general uart or can optionally function as an irda interface. functional overview 50 august 2002 ? revised august 2003 sprs197b the main features of the uart peripherals include: ? selectable uart/autobaud modes (autobauding on uart1 and uart2) ? dual 64-entry fifos for received and transmitted data payload ? programmable and selectable transmit and receive fifo trigger levels for dma and interrupt generation ? programmable sleep mode ? complete status-reporting capabilities in both normal and sleep mode ? frequency prescaler values from 0 to 65535 to generate the appropriate baud rates ? interrupt request generated if multiple system dma requests ? baud rate from 300 bits/s up to 1.5m bits/s ? autobauding between 1200 bits/s and 115.2k bits/s ? software/hardware flow control ? programmable xon/xoff characters ? programmable auto-rts and auto-cts ? programmable serial interface characteristics ? 5-, 6-, 7-, or 8-bit characters ? even-, odd-, or no-parity bit generation and detection ? 1, 1.5, or 2 stop-bit generation ? false start bit detection ? line break generation and detection ? fully prioritized interrupt system controls ? internal test and loopback capabilities ? modem control functions (cts, rts, dsr, dtr) note: dsr and dtr are only available on uart1 and uart3. the irda functions available on uart3 are as follows: ? slow infrared (sir) operations ? framing error, cyclic redundancy check (crc) error, abort pattern (sir) detection ? 8-entry status fifo (with selectable trigger levels) available to monitor frame length and frame errors 3.8.2 general-purpose i/o (gpio) there are up to 14 shared gpio pins on the omap5910 device which may be accessed and controlled by either the dsp public peripheral bus or the mpu public peripheral bus. each gpio pin is independently configurable to be used by either the dsp or mpu. the mpu controls which processor owns each gpio pin by configuring a pin control register that only the mpu can access. each gpio pin can be used as either an input or output pin with gpio inputs being synchronized internally to a peripheral clock. gpio inputs may also optionally be configured to generate an interrupt condition to the processor which owns the gpio pin. the sense of the interrupt condition is configurable such that either a high-to-low or low-to-high transition causes the interrupt condition. some of the gpio pins are multiplexed with other interface pins specific to other device peripherals. refer to table 2?3 to decide which gpio pins are multiplexed with other peripheral signals. 3.8.3 mailbox registers four sets of shared mailbox registers are available for communication between the dsp and mpu. these registers are discussed further in section 3.12, interprocessor communication. functional overview 51 august 2002 ? revised august 2003 sprs197b 3.9 system dma controller the system direct memory access (dma) controller transfers data between points in the memory space without intervention by the mpu. the system dma allows movements of data to and from internal memory, external mem ory, and peripherals to occur in the background of mpu operation. it is designed to off-load the block data transfer function from the mpu processor . the system dma is configured by the mpu via the mpu private peripheral bus. the system dma controller has nine independent general-purpose channels and seven ports that it may transfer to/from. an additional tenth channel is dedicated for use with the lcd controller. of the seven available ports, the dma transfers may occur between any two ports with the exception of the lcd port, which may only be used as a destination with the emiff or imif as the source. for maximum transfer efficiency, all nine channels are independent. this means that if multiple channels are exclusively accessing different ports, then simultaneous transfers performed by the channels will occur uninhibited. if the multiple channels are accessing common ports, however, some arbitration cycles will be necessary. arbitration occurs in a round-robin fashion with configurable priority for each channel (high or low). the basic functional features of the system dma controller are as follows: ? nine general-purpose and one dedicated (lcd) dma channels ? round-robin arbitration scheme with programmable priorities ? concurrent dma transfer capability ? start of transfer on peripheral request or host request ? byte-alignment and byte-packing/unpacking capability ? burst transfer capability (imif, emiff, emifs, lcd, and local ports) ? time-out counter for each dma channel to prevent a channel locking on a memory location or peripheral. ? constant, post-incrementing, and single- or double-indexed addressing modes ? autoinitialization for multiple block transfers without mpu intervention ? access available to all of the memory range (physical memory mapping and tipb space) ? seven ports are available for different kinds of hardware resources. ? emifs port (allowing access to external asynchronous memory or devices) ? emiff port (allowing access to external sdram) ? imif port (allowing access to 192k bytes of shared sram) ? mpui port (allowing access to dsp memory and peripherals) ? tipb port (allowing peripheral register access) ? local port (used for host usb only) ? lcd port (allowing transfers to the lcd controller) ? memory-to-memory transfer granularity of 8, 16, and 32 bits. functional overview 52 august 2002 ? revised august 2003 sprs197b 3.10 dsp dma controller the dsp subsystem has its own dedicated dma controller, which is entirely independent of the mpu or the system dma controller. the dsp dma controller has many of the same major features that the system dma controller possesses (see section 3.9). the dsp dma controller has six generic channels and five physical ports available for source or destination data. these five ports are the saram port, daram port, emif (external memory port), dsp tipb port, and mpui port. the dsp may configure the dsp dma controller to transfer data between the saram, daram, emif, and tipb ports, but the mpui port is a dedicated port used for mpu or system dma initiated transfers to dsp subsystem resources. the saram and daram ports are used to access local dsp memories and the tipb port is used to access the registers of the dsp peripherals. the emif port of the dsp dma controller is used to access the traffic controller via the dsp mmu (memory management unit). 3.11 traffic controller (memory interfaces) the traffic controller (tc) manages all accesses by the mpu, dsp, system dma, and local bus to the omap5910 system memory resources. the tc provides access to three different memory interfaces: external memory interface slow (emifs), external memory interface fast (emiff), and internal memory interface (imif). the imif allows access to the 192k bytes of on-chip sram. the emifs interface provides 16-bit-wide access to asynchronous or synchronous memories or devices, including the following: ? intel ? fast boot block flash (23fxxxf3) ? amd ? simultaneous read/write boot sector flash (am29dlxxxg) ? amd burst-mode flash (am29blxxxc) ? intel strataflash ? memory (28fxxxj3a) ? intel synchronous strataflash memory (28fxxxk3/k18) ? intel wireless flash memory (28fxxxw18) ? asynchronous sram the emiff interface provides access to 16-bit-wide access to standard sdram memories and the imif provides access to the 192k bytes of on-chip sram. the tc provides the functions of arbitrating contending accesses to the same memory interface from dif ferent initiators (mpu, dsp, system dma, local bus), synchronization of accesses due to the initiators and the memory interfaces running at different clock rates, and the buffering of data allowing burst access for more efficient multiplexing of transfers from multiple initiators to the memory interfaces. the tc?s architecture allows simultaneous transfers between initiators and different memory interfaces without penalty. for instance, if the mpu is accessing the emiff at the same time, the dsp is accessing the imif, transfers may occur simultaneously since there is no contention for resources. there are three separate ports to the tc from the system dma (one for each of the memory interfaces), allowing for greater bandwidth capability between the system dma and the tc. intel and intel strataflash are trademarks or registered trademarks of intel corporation or its subsidiaries in the united states and other countries. amd is a trademark of advanced micro devices, inc. functional overview 53 august 2002 ? revised august 2003 sprs197b 3.12 interprocessor communication several mechanisms allow for communication between the mpu and the dsp on the omap5910 device. these include mailbox registers, mpu interface, and shared memory space. 3.12.1 mpu/dsp mailbox registers the mpu and dsp processors may communicate with each other via a mailbox-interrupt mechanism. this mechanism provides a very flexible software protocol between the processors. there are four sets of mailbox registers located in public tipb space. the registers are shared between the two processors, so the mpu and dsp may both access these registers within their own public tipb space, but read/write accessibility of each register is different for each processor. there are four sets of mailbox registers: two for the mpu to send messages and issue an interrupt to the dsp, the other two for the dsp to send messages and issue an interrupt to the mpu. each set of mailbox registers consists of two 16-bit registers and a 1-bit flag register. the interrupting processor can use one 16-bit register to pass a data word to the interrupted processor and the other 16-bit register to pass a command word. communication is achieved when one processor writes to the appropriate command word register which causes an interrupt to the other processor and sets the appropriate flag register. the interrupted processor acknowledges by reading the command word which causes the flag register to be cleared. an additional data-word register is also available in each mailbox register set to optionally communicate two words of data between the processors for each interrupt instead of just communicating the command word. the information communicated by the command and data words are entirely user-defined. the data word may be optionally used to indicate an address pointer or status word. 3.12.2 mpu interface (mpui) the mpu interface (mpui) allows the mpu and the system dma controller to communicate with the dsp and its peripherals. the mpui allows access to the full memory space (16m bytes) of the dsp and the dsp public peripheral bus. thus, the mpu and system dma controller both have read and write access to the complete dsp i/o space (128k bytes), including the control registers of the dsp public peripherals. the mpui port supports the following features: ? four access modes: ? shared-access mode (sam) for mpu access of dsp saram, daram, and external memory interface ? shared-access mode (sam) for peripheral bus access ? host-only mode (hom) for saram access ? host-only mode (hom) for peripheral bus access ? interrupt to mpu if access time-out occurs ? programmable priority scheme (mpu vs. dma) ? packing and unpacking of data (16 bits to 32 bits, and vice versa) ? 32-bit single access support ? software control endianism conversion ? system dma capability to full dsp memory space (16m bytes) ? system dma capability to the dsp public tipb peripherals (up to 128k bytes space) this port can be used for many functions, such as: mpu loading of program code into dsp program memory space, sharing of data between mpu and dsp, implementing interprocessing communication protocols via shared memory, or allowing mpu to use and control dsp public tipb peripherals. functional overview 54 august 2002 ? revised august 2003 sprs197b 3.12.3 mpu/dsp shared memory the omap5910 device implements a shared memory architecture via the traffic controller. therefore, the mpu and dsp both have access to the same shared sram memory (192k bytes) as well as to the emiff and emifs memory space. through the dsp memory management unit (mmu), the mpu controls which regions of shared memory space the dsp is allowed to access. by setting up regions of shared memory, and defining a protocol for the mpu and dsp to access this shared memory, an interprocessor communication mechanism may be implemented. this method may be used in conjunction with the mailbox registers to create handshaking interrupts which will properly synchronize the mpu and dsp accesses to shared memory. utilizing the shared memory in this fashion may be useful when the desired data to be passed between the mpu and dsp is larger than the two 16-bit words provided by each set of mailbox command and data registers. for example, the mpu may need to provide the dsp with a list of pointers to perform a specific task as opposed to a single command and single pointer. using shared memory and the mailboxes, the dsp could read the list of pointers from shared memory after receiving the interrupt caused by an mpu write to the mailbox command register. 3.13 dsp hardware accelerators the tms320c55x dsp core within the omap5910 device utilizes three powerful hardware accelerator modules which assist the dsp core in implementing specific algorithms that are commonly used in video compression applications su ch as mpeg4 encoders/decoders. these accelerators allow implementation of such algorithms using fewer dsp instruction cycles and dissipating less power than implementations using only the dsp core. the hardware accelerators are utilized via functions from the tms320c55x image/video processing library available from texas instruments. utilizing the hardware accelerators, the t exas instruments image/video processing library implements many useful functions, which include the following: ? forward and inverse discrete cosine transform (dct) (used for video compression/decompression) ? motion estimation (used for compression standards such as mpeg video encoding and h.26x encoding) ? pixel interpolation (enabling high-performance fractal-pixel motion estimation) ? quantization/dequantization (useful for jpeg, mpeg, h.26x encoding/decoding) ? flexible 1d/2d wavelet processing (useful for jpeg2000, mpeg4, and other compression standards) ? boundary and perimeter computation (useful for machine vision applications) ? image threshold and histogram computations (useful for various image analysis applications) 3.13.1 dct/idct accelerator the dct/idct hardware accelerator is used to implement forward and inverse dct (discrete cosine transform) algorithms. these dct/idct algorithms can be used to implement a wide range of video compression standards including jpeg encode/decode, mpeg video encode/decode, and h.26x encode/decode. 3.13.2 motion estimation accelerator the motion estimation hardware accelerator implements a high-performance motion estimation algorithm, enabling mpeg video encoder or h.26x encoder applications. motion estimation is typically one of the most computation-intensive operations in video-encoding systems. 3.13.3 pixel interpolation accelerator the pixel interpolation accelerator enables high-performance pixel-interpolation algorithms, which allows for powerful fractal pixel motion estimation when used in conjunction with the motion estimation accelerator. such algorithms provide significant improvement to video-encoding applications. functional overview 55 august 2002 ? revised august 2003 sprs197b 3.14 power supply connection examples 3.14.1 core and i/o voltage supply connections the omap5910 device is extremely flexible regarding the implementation of the core and i/o voltage supplies of the device. in a typical system, all of the core voltage supplies (cv ddx ) may be connected together and powered from one common supply. likewise, all of the i/o voltage supplies (dv ddx ) may be connected together and powered from a common supply. figure 3?4 illustrates this common system configuration. 1.6-v cv dd cv dd4 cv dd3 cv dd2 cv dd1 cv dda dv dd1 dv dd2 dv dd3 dv dd4 dv dd5 v ss omap5910 voltage supply v out = 1.6 v 3.3-v voltage supply v out = 3.3 v figure 3?4. supply connections for a typical system several of the i/o voltage supplies (dv dd3 , dv dd4 and dv dd5 ) are capable of operating at lower voltages (1.8 v nominal) while the other i/o supplies run at 3.3 v nominal. this is advantageous for systems which mix standard 3.3-v devices with low voltage memory devices or other low voltage logic. refer to table 2?2 to determine which i/o pins are powered by each of the dv ddx supplies. figure 3?5 illustrates an example of this type of mixed voltage system configuration. functional overview 56 august 2002 ? revised august 2003 sprs197b 1.6-v cv dd cv dd4 cv dd3 cv dd2 cv dd1 cv dda dv dd1 dv dd2 dv dd3 dv dd4 dv dd5 v ss omap5910 voltage supply v out = 1.6 v 3.3-v voltage supply v out = 3.3 v 1.8-v voltage supply v out = 1.8 v figure 3?5. supply connections for a system with 1.8-v sdram in the previous two examples, all cv ddx pins are connected in common. however, the omap5910 device has dedicated cv dd pins which supply power to different sections of the chip (as described in table 2?3, signal descriptions). this feature could be useful in prototyping phases to troubleshoot power management features and perform advanced power. by isolating each cv ddx bus from the power source through isolation jumpers or current sense resistors, the current draw into dif ferent domains may be measured separately. this type of supply isolation should only be done during prototyping as production system designs should connect all the cv ddx pins together, preferably to a common board plane. note: there is no specific power sequencing for the different voltage supplies as long as all cv ddx and dv ddx voltages are ramped to valid operating levels within 500 ms of one another. additionally, if certain i/o pins are unused in a specific system application, the dv ddx supply pins which power these i/o must still be connected to valid operating voltage levels. see section 5.2, recommended operating conditions , for complete voltage requirements on all cv ddx and dv ddx power supply pins. 3.14.2 core voltage noise isolation two of the cv dd pins on the omap5910 device, cv dda and cv dd4 , are dedicated to supply power for the ulpd dpll and omap dpll, respectively. in addition to using sound board design principles, these dedicated pins allow for added supply noise isolation circuitry to enable maximum performance from the omap5910 dplls. an example circuit is shown in figure 3?6. functional overview 57 august 2002 ? revised august 2003 sprs197b c = 10 f v dd ulpd dpll cv dd4 voltage regulator common cv dd for rest of chip r = 10 ? v ss ? omap5910 cv ddx dedicated cv dd for usb dpll cv dda omap dpll (for usb) dedicated cv dd for ulpd dpll ? this circuit is provided only as an example. specific board layout implementation must minimize noise on the omap5910 voltage s upply pins. ? except where stated otherwise in this document, all v ss pins on the omap5910 are common and must be connected directly to a common ground; however, the discrete capacitor in the rc filter circuit should be placed as close as possible to the v ss (gzg balls aa1/y3 or gdy balls e13/k9). for special consideration with respect to the connection of v ss (gzg ball v12 or gdy ball f6), refer to section 5.6.1, 32-khz oscillator and input clock . ? the voltage regulator must be selected to provide a voltage source with minimal low frequency noise. figure 3?6. external rc circuit for dpll cv dd noise isolation ? 3.15 mpu register descriptions the following tables describe the mpu registers including register addresses, descriptions, required access widths, access types (r = read, w = write, rw = read/write) and reset values. these tables are organized by function with like peripherals or functions together and are therefore not necessarily in the order of ascending register addresses. note: all accesses to these registers must be of the data access widths indicated to avoid a tipb bus error condition and a corresponding interrupt. reserved addresses should never be accessed. functional overview 58 august 2002 ? revised august 2003 sprs197b 3.15.1 mpu private peripheral registers the mpu private peripheral registers include the following: ? timers ? mpu timer 1 register ? mpu timer 2 registers ? mpu timer 3 registers ? mpu watchdog timer registers ? interrupt handlers ? mpu level 1 interrupt handler registers ? mpu level 2 interrupt handler registers ? system peripherals ? system dma controller registers ? lcd controller registers table 3?14. mpu timer 1 registers byte address register name description access width access type reset value fffe:c500 mpu_cntl_timer_1 mpu timer 1 control timer register 32 rw 0000 0000h fffe:c504 mpu_load_tim_1 mpu timer 1 load timer register 32 w undef fffe:c508 mpu_read_tim_1 mpu timer 1 read timer register 32 r undef table 3?15. mpu timer 2 registers byte address register name description access width access type reset value fffe:c600 mpu_cntl_timer_2 mpu timer 2 control timer register 32 rw 0000 0000h fffe:c604 mpu_load_tim_2 mpu timer 2 load timer register 32 w undef fffe:c608 mpu_read_tim_2 mpu timer 2 read timer register 32 r undef table 3?16. mpu timer 3 registers byte address register name description access width access type reset value fffe:c700 mpu_cntl_timer_3 mpu timer 3 control timer register 32 rw 0000 0000h fffe:c704 mpu_load_tim_3 mpu timer 3 load timer register 32 w undef fffe:c708 mpu_read_tim_3 mpu timer 3 read timer register 32 r undef table 3?17. mpu watchdog timer registers byte address register name description access width access type reset value fffe:c800 mpu_cntl_timer_wd mpu wdt control timer register 32 rw 0002h fffe:c804 mpu_load_tim_wd mpu wdt load timer register 32 w ffffh fffe:c808 mpu_read_tim_wd mpu wdt read timer register 32 r ffffh fffe:c80c mpu_timer_mode_wd mpu wdt timer mode register 32 rw 8000h functional overview 59 august 2002 ? revised august 2003 sprs197b table 3?18. mpu level 1 interrupt handler registers byte address register name description access width access type reset value fffe:cb00 mpu_l1_itr interrupt register 32 rw 0000 0000h fffe:cb04 mpu_l1_mir mask interrupt register 32 rw ffff ffffh fffe:cb08 ? fffe:cb0c reserved fffe:cb10 mpu_l1_sir_irq_code irq interrupt encoded source register 32 r 0000 0000h fffe:cb14 mpu_l1_sir_fiq_code fiq interrupt encoded source register 32 r 0000 0000h fffe:cb18 mpu_l1_control_reg interrupt control register 32 rw 0000 0000h fffe:cb1c mpu_l1_ilr0 interrupt 0 priority level register 32 rw 0000 0000h fffe:cb20 mpu_l1_ilr1 interrupt 1 priority level register 32 rw 0000 0000h fffe:cb24 mpu_l1_ilr2 interrupt 2 priority level register 32 rw 0000 0000h fffe:cb28 mpu_l1_ilr3 interrupt 3 priority level register 32 rw 0000 0000h fffe:cb2c mpu_l1_ilr4 interrupt 4 priority level register 32 rw 0000 0000h fffe:cb30 mpu_l1_ilr5 interrupt 5 priority level register 32 rw 0000 0000h fffe:cb34 mpu_l1_ilr6 interrupt 6 priority level register 32 rw 0000 0000h fffe:cb38 mpu_l1_ilr7 interrupt 7 priority level register 32 rw 0000 0000h fffe:cb3c mpu_l1_ilr8 interrupt 8 priority level register 32 rw 0000 0000h fffe:cb40 mpu_l1_ilr9 interrupt 9 priority level register 32 rw 0000 0000h fffe:cb44 mpu_l1_ilr10 interrupt 10 priority level register 32 rw 0000 0000h fffe:cb48 mpu_l1_ilr11 interrupt 11 priority level register 32 rw 0000 0000h fffe:cb4c mpu_l1_ilr12 interrupt 12 priority level register 32 rw 0000 0000h fffe:cb50 mpu_l1_ilr13 interrupt 13 priority level register 32 rw 0000 0000h fffe:cb54 mpu_l1_ilr14 interrupt 14 priority level register 32 rw 0000 0000h fffe:cb58 mpu_l1_ilr15 interrupt 15 priority level register 32 rw 0000 0000h fffe:cb5c mpu_l1_ilr16 interrupt 16 priority level register 32 rw 0000 0000h fffe:cb60 mpu_l1_ilr17 interrupt 17 priority level register 32 rw 0000 0000h fffe:cb64 mpu_l1_ilr18 interrupt 18 priority level register 32 rw 0000 0000h fffe:cb68 mpu_l1_ilr19 interrupt 19 priority level register 32 rw 0000 0000h fffe:cb6c mpu_l1_ilr20 interrupt 20 priority level register 32 rw 0000 0000h fffe:cb70 mpu_l1_ilr21 interrupt 21 priority level register 32 rw 0000 0000h fffe:cb74 mpu_l1_ilr22 interrupt 22 priority level register 32 rw 0000 0000h fffe:cb78 mpu_l1_ilr23 interrupt 23 priority level register 32 rw 0000 0000h fffe:cb7c mpu_l1_ilr24 interrupt 24 priority level register 32 rw 0000 0000h fffe:cb80 mpu_l1_ilr25 interrupt 25 priority level register 32 rw 0000 0000h fffe:cb84 mpu_l1_ilr26 interrupt 26 priority level register 32 rw 0000 0000h fffe:cb88 mpu_l1_ilr27 interrupt 27 priority level register 32 rw 0000 0000h fffe:cb8c mpu_l1_ilr28 interrupt 28 priority level register 32 rw 0000 0000h fffe:cb90 mpu_l1_ilr29 interrupt 29 priority level register 32 rw 0000 0000h fffe:cb94 mpu_l1_ilr30 interrupt 30 priority level register 32 rw 0000 0000h fffe:cb98 mpu_l1_ilr31 interrupt 31 priority level register 32 rw 0000 0000h fffe:cb9c mpu_l1_isr software interrupt set register 32 rw 0000 0000h functional overview 60 august 2002 ? revised august 2003 sprs197b table 3?19. mpu level 2 interrupt handler registers byte address register name description access width access type reset value fffe:0000 mpu_l2_itr interrupt register 32 rw 0000 0000h fffe:0004 mpu_l2_mir mask interrupt register 32 rw ffff ffffh fffe:0008 ? fffe:000c reserved fffe:0010 mpu_l2_sir_irq_code irq interrupt encoded source register 32 r 0000 0000h fffe:0014 mpu_l2_sir_fiq_code fiq interrupt encoded source register 32 r 0000 0000h fffe:0018 mpu_l2_control_reg interrupt control register 32 rw 0000 0000h fffe:001c mpu_l2_ilr0 interrupt 0 priority level register 32 rw 0000 0000h fffe:0020 mpu_l2_ilr1 interrupt 1 priority level register 32 rw 0000 0000h fffe:0024 mpu_l2_ilr2 interrupt 2 priority level register 32 rw 0000 0000h fffe:0028 mpu_l2_ilr3 interrupt 3 priority level register 32 rw 0000 0000h fffe:002c mpu_l2_ilr4 interrupt 4 priority level register 32 rw 0000 0000h fffe:0030 mpu_l2_ilr5 interrupt 5 priority level register 32 rw 0000 0000h fffe:0034 mpu_l2_ilr6 interrupt 6 priority level register 32 rw 0000 0000h fffe:0038 mpu_l2_ilr7 interrupt 7 priority level register 32 rw 0000 0000h fffe:003c mpu_l2_ilr8 interrupt 8 priority level register 32 rw 0000 0000h fffe:0040 mpu_l2_ilr9 interrupt 9 priority level register 32 rw 0000 0000h fffe:0044 mpu_l2_ilr10 interrupt 10 priority level register 32 rw 0000 0000h fffe:0048 mpu_l2_ilr11 interrupt 11 priority level register 32 rw 0000 0000h fffe:004c mpu_l2_ilr12 interrupt 12 priority level register 32 rw 0000 0000h fffe:0050 mpu_l2_ilr13 interrupt 13 priority level register 32 rw 0000 0000h fffe:0054 mpu_l2_ilr14 interrupt 14 priority level register 32 rw 0000 0000h fffe:0058 mpu_l2_ilr15 interrupt 15 priority level register 32 rw 0000 0000h fffe:005c mpu_l2_ilr16 interrupt 16 priority level register 32 rw 0000 0000h fffe:0060 mpu_l2_ilr17 interrupt 17 priority level register 32 rw 0000 0000h fffe:0064 mpu_l2_ilr18 interrupt 18 priority level register 32 rw 0000 0000h fffe:0068 mpu_l2_ilr19 interrupt 19 priority level register 32 rw 0000 0000h fffe:006c mpu_l2_ilr20 interrupt 20 priority level register 32 rw 0000 0000h fffe:0070 mpu_l2_ilr21 interrupt 21 priority level register 32 rw 0000 0000h fffe:0074 mpu_l2_ilr22 interrupt 22 priority level register 32 rw 0000 0000h fffe:0078 mpu_l2_ilr23 interrupt 23 priority level register 32 rw 0000 0000h fffe:007c mpu_l2_ilr24 interrupt 24 priority level register 32 rw 0000 0000h fffe:0080 mpu_l2_ilr25 interrupt 25 priority level register 32 rw 0000 0000h fffe:0084 mpu_l2_ilr26 interrupt 26 priority level register 32 rw 0000 0000h fffe:0088 mpu_l2_ilr27 interrupt 27 priority level register 32 rw 0000 0000h fffe:008c mpu_l2_ilr28 interrupt 28 priority level register 32 rw 0000 0000h fffe:0090 mpu_l2_ilr29 interrupt 29 priority level register 32 rw 0000 0000h fffe:0094 mpu_l2_ilr30 interrupt 30 priority level register 32 rw 0000 0000h fffe:0098 mpu_l2_ilr31 interrupt 31 priority level register 32 rw 0000 0000h fffe:009c mpu_l2_isr software interrupt set register 32 rw 0000 0000h functional overview 61 august 2002 ? revised august 2003 sprs197b table 3?20. system dma controller registers byte address register name description access width access type reset value fffe:d800 sys_dma_csdp_ch0 channel 0 source/destination parameters register 16 rw 0000h fffe:d802 sys_dma_ccr_ch0 channel 0 control register 16 rw 0000h fffe:d804 sys_dma_cicr_ch0 channel 0 interrupt control register 16 rw 0003h fffe:d806 sys_dma_csr_ch0 channel 0 status register 16 r 0000h fffe:d808 sys_dma_cssa_l_ch0 channel 0 source start address register lsb 16 rw undef fffe:d80a sys_dma_cssa_u_ch0 channel 0 source start address register msb 16 rw undef fffe:d80c sys_dma_cdsa_l_ch0 channel 0 destination start address register lsb 16 rw undef fffe:d80e sys_dma_cdsa_u_ch0 channel 0 destination start address register msb 16 rw undef fffe:d810 sys_dma_cen_ch0 channel 0 element number register 16 rw undef fffe:d812 sys_dma_cfn_ch0 channel 0 frame number register 16 rw undef fffe:d814 sys_dma_cfi_ch0 channel 0 frame index register 16 rw undef fffe:d816 sys_dma_cei_ch0 channel 0 element index register 16 rw undef fffe:d818 sys_dma_cpc_ch0 channel 0 progress counter register 16 rw undef fffe:d81a ? fffe:083e reserved fffe:d840 sys_dma_csdp_ch1 channel 1 source/destination parameters register 16 rw 0000h fffe:d842 sys_dma_ccr_ch1 channel 1 control register 16 rw 0000h fffe:d844 sys_dma_cicr_ch1 channel 1 interrupt control register 16 rw 0003h fffe:d846 sys_dma_csr_ch1 channel 1 status register 16 r 0000h fffe:d848 sys_dma_cssa_l_ch1 channel 1 source start address register lsb 16 rw undef fffe:d84a sys_dma_cssa_u_ch1 channel 1 source start address register msb 16 rw undef fffe:d84c sys_dma_cdsa_l_ch1 channel 1 destination start address register lsb 16 rw undef fffe:d84e sys_dma_cdsa_u_ch1 channel 1 destination start address register msb 16 rw undef fffe:d850 sys_dma_cen_ch1 channel 1 element number register 16 rw undef fffe:d852 sys_dma_cfn_ch1 channel 1 frame number register 16 rw undef fffe:d854 sys_dma_cfi_ch1 channel 1 frame index register 16 rw undef fffe:d856 sys_dma_cei_ch1 channel 1 element index register 16 rw undef fffe:d858 sys_dma_cpc_ch1 channel 1 progress counter register 16 rw undef fffe:d85a ? fffe:d87e reserved fffe:d880 sys_dma_csdp_ch2 channel 2 source/destination parameters register 16 rw 0000h fffe:d882 sys_dma_ccr_ch2 channel 2 control register 16 rw 0000h fffe:d884 sys_dma_cicr_ch2 channel 2 interrupt control register 16 rw 0003h fffe:d886 sys_dma_csr_ch2 channel 2 status register 16 r 0000h fffe:d888 sys_dma_cssa_l_ch2 channel 2 source start address register lsb 16 rw undef fffe:d88a sys_dma_cssa_u_ch2 channel 2 source start address register msb 16 rw undef fffe:d88c sys_dma_cdsa_l_ch2 channel 2 destination start address register lsb 16 rw undef fffe:d88e sys_dma_cdsa_u_ch2 channel 2 destination start address register msb 16 rw undef fffe:d890 sys_dma_cen_ch2 channel 2 element number register 16 rw undef fffe:d892 sys_dma_cfn_ch2 channel 2 frame number register 16 rw undef fffe:d894 sys_dma_cfi_ch2 channel 2 frame index register 16 rw undef fffe:d896 sys_dma_cei_ch2 channel 2 element index register 16 rw undef fffe:d898 sys_dma_cpc_ch2 channel 2 progress counter register 16 rw undef functional overview 62 august 2002 ? revised august 2003 sprs197b table 3?20. system dma controller registers (continued) reset value access type access width description register name byte address fffe:d89a ? fffe:d8be reserved fffe:d8c0 sys_dma_csdp_ch3 channel 3 source/destination parameters register 16 rw 0000h fffe:d8c2 sys_dma_ccr_ch3 channel 3 control register 16 rw 0000h fffe:d8c4 sys_dma_cicr_ch3 channel 3 interrupt control register 16 rw 0003h fffe:d8c6 sys_dma_csr_ch3 channel 3 status register 16 r 0000h fffe:d8c8 sys_dma_cssa_l_ch3 channel 3 source start address register lsb 16 rw undef fffe:d8ca sys_dma_cssa_u_ch3 channel 3 source start address register msb 16 rw undef fffe:d8cc sys_dma_cdsa_l_ch3 channel 3 destination start address register lsb 16 rw undef fffe:d8ce sys_dma_cdsa_u_ch3 channel 3 destination start address register msb 16 rw undef fffe:d8d0 sys_dma_cen_ch3 channel 3 element number register 16 rw undef fffe:d8d2 sys_dma_cfn_ch3 channel 3 frame number register 16 rw undef fffe:d8d4 sys_dma_cfi_ch3 channel 3 frame index register 16 rw undef fffe:d8d6 sys_dma_cei_ch3 channel 3 element index register 16 rw undef fffe:d8d8 sys_dma_cpc_ch3 channel 3 progress counter register 16 rw undef fffe:d8da ? fffe:d8fe reserved fffe:d900 sys_dma_csdp_ch4 channel 4 source/destination parameters register 16 rw 0000h fffe:d902 sys_dma_ccr_ch4 channel 4 control register 16 rw 0000h fffe:d904 sys_dma_cicr_ch4 channel 4 interrupt control register 16 rw 0003h fffe:d906 sys_dma_csr_ch4 channel 4 status register 16 r 0000h fffe:d908 sys_dma_cssa_l_ch4 channel 4 source start address register lsb 16 rw undef fffe:d90a sys_dma_cssa_u_ch4 channel 4 source start address register msb 16 rw undef fffe:d90c sys_dma_cdsa_l_ch4 channel 4 destination start address register lsb 16 rw undef fffe:d90e sys_dma_cdsa_u_ch4 channel 4 destination start address register msb 16 rw undef fffe:d910 sys_dma_cen_ch4 channel 4 element number register 16 rw undef fffe:d912 sys_dma_cfn_ch4 channel 4 frame number register 16 rw undef fffe:d914 sys_dma_cfi_ch4 channel 4 frame index register 16 rw undef fffe:d916 sys_dma_cei_ch4 channel 4 element index register 16 rw undef fffe:d918 sys_dma_cpc_ch4 channel 4 progress counter register 16 rw undef fffe:d91a ? fffe:d93e reserved fffe:d940 sys_dma_csdp_ch5 channel 5 source/destination parameters register 16 rw 0000h fffe:d942 sys_dma_ccr_ch5 channel 5 control register 16 rw 0000h fffe:d944 sys_dma_cicr_ch5 channel 5 interrupt control register 16 rw 0003h fffe:d946 sys_dma_csr_ch5 channel 5 status register 16 r 0000h fffe:d948 sys_dma_cssa_l_ch5 channel 5 source start address register lsb 16 rw undef fffe:d94a sys_dma_cssa_u_ch5 channel 5 source start address register msb 16 rw undef fffe:d94c sys_dma_cdsa_l_ch5 channel 5 destination start address register lsb 16 rw undef fffe:d94e sys_dma_cdsa_u_ch5 channel 5 destination start address register msb 16 rw undef fffe:d950 sys_dma_cen_ch5 channel 5 element number register 16 rw undef fffe:d952 sys_dma_cfn_ch5 channel 5 frame number register 16 rw undef fffe:d954 sys_dma_cfi_ch5 channel 5 frame index register 16 rw undef fffe:d956 sys_dma_cei_ch5 channel 5 element index register 16 rw undef functional overview 63 august 2002 ? revised august 2003 sprs197b table 3?20. system dma controller registers (continued) reset value access type access width description register name byte address fffe:d958 sys_dma_cpc_ch5 channel 5 progress counter register 16 rw undef fffe:d95a ? fffe:d97e reserved fffe:d980 sys_dma_csdp_ch6 channel 6 source/destination parameters register 16 rw 0000h fffe:d982 sys_dma_ccr_ch6 channel 6 control register 16 rw 0000h fffe:d984 sys_dma_cicr_ch6 channel 6 interrupt control register 16 rw 0003h fffe:d986 sys_dma_csr_ch6 channel 6 status register 16 r 0000h fffe:d988 sys_dma_cssa_l_ch6 channel 6 source start address register lsb 16 rw undef fffe:d98a sys_dma_cssa_u_ch6 channel 6 source start address register msb 16 rw undef fffe:d98c sys_dma_cdsa_l_ch6 channel 6 destination start address register lsb 16 rw undef fffe:d98e sys_dma_cdsa_u_ch6 channel 6 destination start address register msb 16 rw undef fffe:d990 sys_dma_cen_ch6 channel 6 element number register 16 rw undef fffe:d992 sys_dma_cfn_ch6 channel 6 frame number register 16 rw undef fffe:d994 sys_dma_cfi_ch6 channel 6 frame index register 16 rw undef fffe:d996 sys_dma_cei_ch6 channel 6 element index register 16 rw undef fffe:d998 sys_dma_cpc_ch6 channel 6 progress counter register 16 rw undef fffe:d99a ? fffe:d9be reserved fffe:d9c0 sys_dma_csdp_ch7 channel 7 source/destination parameters register 16 rw 0000h fffe:d9c2 sys_dma_ccr_ch7 channel 7 control register 16 rw 0000h fffe:d9c4 sys_dma_cicr_ch7 channel 7 interrupt control register 16 rw 0003h fffe:d9c6 sys_dma_csr_ch7 channel 7 status register 16 r 0000h fffe:d9c8 sys_dma_cssa_l_ch7 channel 7 source start address register lsb 16 rw undef fffe:d9ca sys_dma_cssa_u_ch7 channel 7 source start address register msb 16 rw undef fffe:d9cc sys_dma_cdsa_l_ch7 channel 7 destination start address register lsb 16 rw undef fffe:d9ce sys_dma_cdsa_u_ch7 channel 7 destination start address register msb 16 rw undef fffe:d9d0 sys_dma_cen_ch7 channel 7 element number register 16 rw undef fffe:d9d2 sys_dma_cfn_ch7 channel 7 frame number register 16 rw undef fffe:d9d4 sys_dma_cfi_ch7 channel 7 frame index register 16 rw undef fffe:d9d6 sys_dma_cei_ch7 channel 7 element index register 16 rw undef fffe:d9d8 sys_dma_cpc_ch7 channel 7 progress counter register 16 rw undef fffe:d9da ? fffe:d9fe reserved fffe:da00 sys_dma_csdp_ch8 channel 8 source/destination parameters register 16 rw 0000h fffe:da02 sys_dma_ccr_ch8 channel 8 control register 16 rw 0000h fffe:da04 sys_dma_cicr_ch8 channel 8 interrupt control register 16 rw 0003h fffe:da06 sys_dma_csr_ch8 channel 8 status register 16 r 0000h fffe:da08 sys_dma_cssa_l_ch8 channel 8 source start address register lsb 16 rw undef fffe:da0a sys_dma_cssa_u_ch8 channel 8 source start address register msb 16 rw undef fffe:da0c sys_dma_cdsa_l_ch8 channel 8 destination start address register lsb 16 rw undef fffe:da0e sys_dma_cdsa_u_ch8 channel 8 destination start address register msb 16 rw undef fffe:da10 sys_dma_cen_ch8 channel 8 element number register 16 rw undef fffe:da12 sys_dma_cfn_ch8 channel 8 frame number register 16 rw undef fffe:da14 sys_dma_cfi_ch8 channel 8 frame index register 16 rw undef functional overview 64 august 2002 ? revised august 2003 sprs197b table 3?20. system dma controller registers (continued) reset value access type access width description register name byte address fffe:da16 sys_dma_cei_ch8 channel 8 element index register 16 rw undef fffe:da18 sys_dma_cpc_ch8 channel 8 progress counter register 16 rw undef fffe:da1a ? fffe:dafe reserved fffe:db00 sys_dma_lcd_ctrl lcd channel control register 16 rw 0000h fffe:db02 sys_dma_lcd_top_f1_l lcd channel top address frame buffer 1 register lsb 16 rw undef fffe:db04 sys_dma_lcd_top_f1_u lcd channel top address frame buffer 1 register msb 16 rw undef fffe:db06 sys_dma_lcd_bot_f1_l lcd channel bottom address frame buffer 1 register lsb 16 rw undef fffe:db08 sys_dma_lcd_bot_f1_u lcd channel bottom address frame buffer 1 register msb 16 rw undef fffe:db0a sys_dma_lcd_top_f2_l lcd channel top address frame buffer 2 register lsb 16 rw undef fffe:db0c sys_dma_lcd_top_f2_u lcd channel top address frame buffer 2 register msb 16 rw undef fffe:db0e sys_dma_lcd_bot_f2_l lcd channel bottom address frame buffer 2 register lsb 16 rw undef fffe:db10 sys_dma_lcd_bot_f2_u lcd channel bottom address frame buffer 2 register msb 16 rw undef fffe:db12 ? fffe:dbfe reserved fffe:dc00 sys_dma_gcr dma global control register 16 rw 0008h table 3?21. lcd controller registers byte address register name description access width access type reset value fffe:c000 lcd_control lcd control register 32 rw 0x0000 0000 fffe:c004 lcd_timing0 lcd timing 0 register 32 rw undef fffe:c008 lcd_timing1 lcd timing 1 register 32 rw 0x0000 0000 fffe:c00c lcd_timing2 lcd timing 2 register 32 rw 0x0000 0000 fffe:c010 lcd_status lcd status register 32 rw 0x0000 0000 fffe:c014 lcd_subpanel lcd subpanel display register 32 rw 0x0000 0000 functional overview 65 august 2002 ? revised august 2003 sprs197b 3.15.2 mpu public peripheral registers the mpu public peripheral registers include the following: ? serial ports ? mcbsp2 registers ? microwire registers ?i 2 c registers ? hdq/1-wire interface registers ? mmc/sd registers ? usb function registers ? usb host registers ? parallel ports ? camera interface registers ? human interface support ? mpuio/keyboard registers ? pwl registers ? pwt registers ? led pulse generator 1 registers ? led pulse generator 2 registers ? timers and counters ? 32k timer registers ? real-time clock registers ? frame adjustment counter registers functional overview 66 august 2002 ? revised august 2003 sprs197b table 3?22. mcbsp2 registers byte address register name description access width access type reset value fffb:1000 mcbsp2_drr2 mcbsp2 data receive register 2 16 rw 0000h fffb:1002 mcbsp2_drr1 mcbsp2 data receive register 1 16 rw 0000h fffb:1004 mcbsp2_dxr2 mcbsp2 data transmit register 2 16 rw 0000h fffb:1006 mcbsp2_dxr1 mcbsp2 data transmit register 1 16 rw 0000h fffb:1008 mcbsp2_spcr2 mcbsp2 serial port control register 2 16 rw 0000h fffb:100a mcbsp2_spcr1 mcbsp2 serial port control register 1 16 rw 0000h fffb:100c mcbsp2_rcr2 mcbsp2 receive control register 2 16 rw 0000h fffb:100e mcbsp2_rcr1 mcbsp2 receive control register 1 16 rw 0000h fffb:1010 mcbsp2_xcr2 mcbsp2 transmit control register 2 16 rw 0000h fffb:1012 mcbsp2_xcr1 mcbsp2 transmit control register 1 16 rw 0000h fffb:1014 mcbsp2_srgr2 mcbsp2 sample rate generator register 2 16 rw 2000h fffb:1016 mcbsp2_srgr1 mcbsp2 sample rate generator register 1 16 rw 0001h fffb:1018 mcbsp2_mcr2 mcbsp2 multichannel register 2 16 rw 0000h fffb:101a mcbsp2_mcr1 mcbsp2 multichannel register 1 16 rw 0000h fffb:101c mcbsp2_rcera mcbsp2 receive channel enable register partition a 16 rw 0000h fffb:101e mcbsp2_rcerb mcbsp2 receive channel enable register partition b 16 rw 0000h fffb:1020 mcbsp2_xcera mcbsp2 transmit channel enable register partition a 16 rw 0000h fffb:1022 mcbsp2_xcerb mcbsp2 transmit channel enable register partition b 16 rw 0000h fffb:1024 mcbsp2_pcr0 mcbsp2 pin control register 0 16 rw 0000h fffb:1026 mcbsp2_rcerc mcbsp2 receive channel enable register partition c 16 rw 0000h fffb:1028 mcbsp2_rcerd mcbsp2 receive channel enable register partition d 16 rw 0000h fffb:102a mcbsp2_xcerc mcbsp2 transmit channel enable register partition c 16 rw 0000h fffb:102c mcbsp2_xcerd mcbsp2 transmit channel enable register partition d 16 rw 0000h fffb:102e mcbsp2_rcere mcbsp2 receive channel enable register partition e 16 rw 0000h fffb:1030 mcbsp2_rcerf mcbsp2 receive channel enable register partition f 16 rw 0000h fffb:1032 mcbsp2_xcere mcbsp2 transmit channel enable register partition e 16 rw 0000h fffb:1034 mcbsp2_xcerf mcbsp2 transmit channel enable register partition f 16 rw 0000h fffb:1036 mcbsp2_rcerg mcbsp2 receive channel enable register partition g 16 rw 0000h fffb:1038 mcbsp2_rcerh mcbsp2 receive channel enable register partition h 16 rw 0000h fffb:103a mcbsp2_xcerg mcbsp2 transmit channel enable register partition g 16 rw 0000h fffb:103c mcbsp2_xcerh mcbsp2 transmit channel enable register partition h 16 rw 0000h table 3?23. microwire registers byte address register name description access width access type reset value fffb:3000 td microwire transmit data register 16 w undef fffb:3000 rd microwire receive data register 16 r undef fffb:3004 csr microwire control and status register 16 rw undef fffb:3008 sr1 microwire setup register 1 16 rw undef fffb:300c sr2 microwire setup register 2 16 rw undef fffb:3010 sr3 microwire setup register 3 16 rw 0000h fffb:3014 sr4 microwire setup register 4 16 rw 0000h fffb:3018 sr5 microwire setup register 5 16 rw 0000h functional overview 67 august 2002 ? revised august 2003 sprs197b table 3?24. i 2 c registers byte address register name description access width access type reset value fffb:3800 i2c_rev i 2 c module version register 16 rw 0011h fffb:3804 i2c_ie i 2 c interrupt enable register 16 rw 0000h fffb:3808 i2c_stat i 2 c status register 16 r 0000h fffb:380c i2c_iv i 2 c interrupt vector register 16 r 0000h fffb:3810 reserved fffb:3814 i2c_buf i 2 c buffer configuration register 16 rw 0000h fffb:3818 i2c_cnt i 2 c data counter register 16 rw 0000h fffb:381c i2c_data i 2 c data access register 16 rw 0000h fffb:3820 reserved fffb:3824 i2c_con i 2 c configuration register 16 rw 0000h fffb:3828 i2c_oa i 2 c own address register 16 rw 0000h fffb:382c i2c_sa i 2 c slave address register 16 rw 03ffh fffb:3830 i2c_psc i 2 c clock prescaler register 16 rw 0000h fffb:3834 i2c_scll i 2 c scl low timer register 16 rw 0000h fffb:3838 i2c_sclh i 2 c scl high timer register 16 rw 0000h fffb:383c i2c_systest i 2 c system test register 16 rw 0000h table 3?25. hdq/1-wire interface registers byte address register name description access width access type reset value fffb:c000 txr tx write data register 8 rw 00h fffb:c004 rxr rx receive buffer register 8 r undef fffb:c008 csr control and status register 8 rw 00h fffb:c00c isr interrupt status register 8 rw 00h functional overview 68 august 2002 ? revised august 2003 sprs197b table 3?26. mmc/sd registers byte address register name description access width access type reset value fffb:7800 mmc_cmd mmc command 16 rw 0000h fffb:7804 mmc_argl mmc argument low 16 rw 0000h fffb:7808 mmc_argh mmc argument high 16 rw 0000h fffb:780c mmc_con mmc system configuration 16 rw 0000h fffb:7810 mmc_stat mmc status 16 rw 0000h fffb:7814 mmc_ie mmc system interrupt enable 16 rw 0000h fffb:7818 mmc_cto mmc command timeout 16 rw 0000h fffb:781c mmc_dto mmc data timeout 16 rw 0000h fffb:7820 mmc_data mmc tx/rx fifo data 16 rw 0000h fffb:7824 mmc_blen mmc block length 16 rw 0000h fffb:7828 mmc_nblk mmc number of blocks 16 rw 0000h fffb:782c mmc_buf mmc buffer configuration 16 rw 1f00h fffb:7830 mmc_spi mmc serial port interface 16 rw 0000h fffb:7834 mmc_sdio mmc sdio mode configuration 16 rw 0000h fffb:7838 mmc_syst mmc system test 16 rw 2000h fffb:783c mmc_rev mmc module version 16 r ? fffb:7840 mmc_rsp0 mmc command response 0 16 r undef fffb:7844 mmc_rsp1 mmc command response 1 16 r undef fffb:7848 mmc_rsp2 mmc command response 2 16 r undef fffb:784c mmc_rsp3 mmc command response 3 16 r undef fffb:7850 mmc_rsp4 mmc command response 4 16 r undef fffb:7854 mmc_rsp5 mmc command response 5 16 r undef fffb:7858 mmc_rsp6 mmc command response 6 16 r undef fffb:785c mmc_rsp7 mmc command response 7 16 r undef functional overview 69 august 2002 ? revised august 2003 sprs197b table 3?27. usb function registers byte address register name description access width access type reset value fffb:4000 rev revision register 16 r ? fffb:4004 ep_num endpoint selection register 16 rw 0000h fffb:4008 data data register 16 rw undef fffb:400c ctrl control register 16 rw 0000h fffb:4010 stat_flg status flag register 16 r 0202h fffb:4014 rxfstat receive fifo status register 16 r 0000h fffb:4018 syscon1 system configuration 1 register 16 rw 0000h fffb:401c syscon2 system configuration 2 register 16 rw 0000h fffb:4020 devstat device status register 16 r undef fffb:4024 sof start of frame register 16 r 0000h fffb:4028 irq_en interrupt enable register 16 rw undef fffb:402c dma_irq_en dma interrupt enable register 16 rw undef fffb:4030 irq_src interrupt source register 16 rw 0000h fffb:4034 epn_stat endpoint interrupt status register 16 r 0000h fffb:4038 dman_stat dma endpoint interrupt status register 16 r 0000h fffb:403c reserved fffb:4040 rxdma_cfg receive channels dma configuration register 16 rw 0000h fffb:4044 txdma_cfg transmit channels dma configuration register 16 rw 0000h fffb:4048 data_dma dma fifo data register 16 rw undef fffb:404c reserved fffb:4050 txdma0 transmit dma control 0 register 16 rw 0000h fffb:4054 txdma1 transmit dma control 1 register 16 rw 0000h fffb:4058 txdma2 transmit dma control 2 register 16 rw 0000h fffb:405c reserved fffb:4060 rxdma0 receive dma control 0 register 16 rw 0000h fffb:4064 rxdma1 receive dma control 1 register 16 rw 0000h fffb:4068 rxdma2 receive dma control 2 register 16 rw 0000h fffb:406c ? fffb:407c reserved fffb:4080 ep0 endpoint configuration 0 register 16 rw 0000h fffb:4084 ep1_rx receive endpoint configuration 1 register 16 rw undef fffb:4088 ep2_rx receive endpoint configuration 2 register 16 rw undef fffb:408c ep3_rx receive endpoint configuration 3 register 16 rw undef fffb:4090 ep4_rx receive endpoint configuration 4 register 16 rw undef fffb:4094 ep5_rx receive endpoint configuration 5 register 16 rw undef fffb:4098 ep6_rx receive endpoint configuration 6 register 16 rw undef fffb:409c ep7_rx receive endpoint configuration 7 register 16 rw undef fffb:40a0 ep8_rx receive endpoint configuration 8 register 16 rw undef fffb:40a4 ep9_rx receive endpoint configuration 9 register 16 rw undef fffb:40a8 ep10_rx receive endpoint configuration 10 register 16 rw undef fffb:40ac ep11_rx receive endpoint configuration 11 register 16 rw undef fffb:40b0 ep12_rx receive endpoint configuration 12 register 16 rw undef fffb:40b4 ep13_rx receive endpoint configuration 13 register 16 rw undef fffb:40b8 ep14_rx receive endpoint configuration 14 register 16 rw undef functional overview 70 august 2002 ? revised august 2003 sprs197b table 3?27. usb function registers (continued) byte address reset value access type access width description register name fffb:40bc ep15_rx receive endpoint configuration 15 register 16 rw undef fffb:40c0 reserved fffb:40c4 ep1_tx transmit endpoint configuration 1 register 16 rw undef fffb:40c8 ep2_tx transmit endpoint configuration 2 register 16 rw undef fffb:40cc ep3_tx transmit endpoint configuration 3 register 16 rw undef fffb:40d0 ep4_tx transmit endpoint configuration 4 register 16 rw undef fffb:40d4 ep5_tx transmit endpoint configuration 5 register 16 rw undef fffb:40d8 ep6_tx transmit endpoint configuration 6 register 16 rw undef fffb:40dc ep7_tx transmit endpoint configuration 7 register 16 rw undef fffb:40e0 ep8_tx transmit endpoint configuration 8 register 16 rw undef fffb:40e4 ep9_tx transmit endpoint configuration 9 register 16 rw undef fffb:40e8 ep10_tx transmit endpoint configuration 10 register 16 rw undef fffb:40ec ep11_tx transmit endpoint configuration 11 register 16 rw undef fffb:40f0 ep12_tx transmit endpoint configuration 12 register 16 rw undef fffb:40f4 ep13_tx transmit endpoint configuration 13 register 16 rw undef fffb:40f8 ep14_tx transmit endpoint configuration 14 register 16 rw undef fffb:40fc ep15_tx transmit endpoint configuration 15 register 16 rw undef functional overview 71 august 2002 ? revised august 2003 sprs197b table 3?28. usb host controller registers byte address register name description access width access type reset value fffb:a000 hcrevision ohci revision register 32 r 0000 0010h fffb:a004 hccontrol host controller operating mode register 32 rw 0000 0000h fffb:a008 hccommandstatus host controller command and status register 32 rw 0000 0000h fffb:a00c hcinterruptstatus host controller interrupt status register 32 rw 0000 0000h fffb:a010 hcinterruptenable host controller interrupt enable register 32 rw 0000 0000h fffb:a014 hcinterruptdisable host controller interrupt disable register 32 r 0000 0000h fffb:a018 hchcca lb virtual address hcca register 32 rw 0000 0000h fffb:a01c hcperiodcurrented lb virtual address current periodic ep descriptor register 32 rw 0000 0000h fffb:a020 hccontrolheaded lb virtual address control ep descriptor list head register 32 rw 0000 0000h fffb:a024 hccontrolcurrented lb virtual address current control ep descriptor register 32 rw 0000 0000h fffb:a028 hcbulkheaded lb virtual address bulk ep descriptor list head register 32 rw 0000 0000h fffb:a02c hcbulkcurrented lb virtual address current bulk ep descriptor register 32 rw 0000 0000h fffb:a030 hcdonehead lb virtual address retired transfer descriptor list head register 32 r undef fffb:a034 hcfminterval frame interval register 32 rw 0000 2edfh fffb:a038 hcfmremaining remaining frame time register 32 r 0000 0000h fffb:a03c hcfmnumber remaining frame number register 32 r 0000 0000h fffb:a040 hcperiodicstart periodic start time register 32 rw 0000 0000h fffb:a044 hclsthreshold low speed start threshold register 32 rw 0000 0628h fffb:a048 hcrhdescriptora usb root hub descriptor register a 32 rw 0a00 1203h fffb:a04c hcrhdescriptorb usb root hub descriptor register b 32 rw 0000 0000h fffb:a050 hcrhstatus usb root hub status register 32 rw 0000 0000h fffb:a054 hcrhportstatus1 port 1 control and status register 32 rw 0000 0100h fffb:a058 hcrhportstatus2 port 2 control and status register 32 rw 0000 0100h fffb:a05c hcrhportstatus3 port 3 control and status register 32 rw 0000 0100h fffb:a060 ? fffb:a0dc reserved fffb:a0e0 hostueaddr lb virtual address last unrecoverable error register 32 r 0000 0000h fffb:a0e4 hostuestatus lb cycle type last unrecoverable error register 32 r 0000 0000h fffb:a0e8 hosttimeoutctrl usb host mastered local bus time-out enable register 32 rw 0000 0000h fffb:a0ec hostrevision usb host controller revision register 32 r ? table 3?29. camera interface registers byte address register name description access width access type reset value fffb:6800 ctrlclock clock control register 32 rw 0000 0000h fffb:6804 it_status interrupt status register 32 r 0000 0000h fffb:6808 mode mode configuration register 32 rw 0000 0200h fffb:680c status status register 32 r 0000 0000h fffb:6810 camdata image data register 32 r 0000 0000h fffb:6814 gpio gpio register 32 rw 0000 0000h fffb:6818 peak_counter fifo peak counter register 32 rw 0000 0000h functional overview 72 august 2002 ? revised august 2003 sprs197b table 3?30. mpu i/o/keyboard registers byte address register name description access width access type reset value fffb:5000 input_latch input register 16 r undef fffb:5004 output_reg output register 16 rw undef fffb:5008 io_cntl input output control register 16 rw ffffh fffb:500c reserved fffb:5010 kbr_latch keyboard row inputs register 16 r undef fffb:5014 kbc_reg keyboard column outputs register 16 rw 0000h fffb:5018 gpio_event_mode gpio event mode register 16 rw 0000h fffb:501c gpio_int_edge gpio interrupt edge register 16 rw 0000h fffb:5020 kbd_int keyboard interrupt register 16 r 0000h fffb:5024 gpio_int gpio interrupt register 16 r 0000h fffb:5028 kbd_maskit keyboard mask interrupt register 16 rw 0000h fffb:502c gpio_maskit gpio mask interrupt register 16 rw 0000h fffb:5030 gpio_debouncing gpio debouncing register 16 rw 0000h fffb:5034 gpio_latch gpio latch register 16 r 0000h table 3?31. pwl registers byte address register name description access width access type reset value fffb:5800 pwl_level pwl level register 8 rw 0000h fffb:5804 pwl_ctrl pwl control register 8 rw 0000h table 3?32. pwt registers byte address register name description access width access type reset value fffb:6000 pwt_frc pwt frequency control register 8 rw 0000h fffb:6004 pwt_vcr pwt volume control register 8 rw 0000h fffb:6008 pwt_gcr pwt general control register 8 rw 0000h table 3?33. led pulse generator 1 registers byte address register name description access width access type reset value fffb:d000 lcr_1 lpg1 control register 8 rw 00h fffb:d004 pmr_1 lpg1 power management register 8 rw 00h table 3?34. led pulse generator 2 registers byte address register name description access width access type reset value fffb:d800 lcr_2 lpg2 control register 8 rw 00h fffb:d804 pmr_2 lpg2 power management register 8 rw 00h table 3?35. 32k timer registers byte address register name description access width access type reset value fffb:9000 tvr tick value register 32 rw 00ff ffffh fffb:9004 tcr tick counter register 32 r 00ff ffffh fffb:9008 cr control register 32 rw 0000 0008h functional overview 73 august 2002 ? revised august 2003 sprs197b table 3?36. real-time clock registers byte address register name description access width access type reset value fffb:4800 seconds_reg rtc seconds register 8 rw 00h fffb:4804 minutes_reg rtc minutes register 8 rw 00h fffb:4808 hours_reg rtc hours register 8 rw 00h fffb:480c days_reg rtc days register 8 rw 01h fffb:4810 months_reg rtc months register 8 rw 01h fffb:4814 years_reg rtc years register 8 rw 00h fffb:4818 week_reg rtc weeks register 8 rw 00h fffb:481c reserved fffb:4820 alarm_second_reg rtc alarm seconds register 8 rw 00h fffb:4824 alarm_minutes_reg rtc alarm minutes register 8 rw 00h fffb:4828 alarm_hours_reg rtc alarm hours register 8 rw 00h fffb:482c alarm_days_reg rtc alarm days register 8 rw 01h fffb:4830 alarm_months_reg rtc alarm months register 8 rw 01h fffb:4834 alarm_years_reg rtc alarm years register 8 rw 00h fffb:4838 ? fffb:483c reserved fffb:4840 rtc_ctrl_reg rtc control register 8 rw 00h fffb:4844 rtc_status_reg rtc status register 8 rw 00h fffb:4848 rtc_interrupts_reg rtc interrupts register 8 rw 00h fffb:484c rtc_comp_lsb_reg rtc compensation lsb register 8 rw 00h fffb:4850 rtc_comp_msb_reg rtc compensation msb register 8 rw 00h table 3?37. frame adjustment counter registers byte address register name description access width access type reset value fffb:a800 farc frame adjustment reference count register 16 rw 0000h fffb:a804 fsc frame start count register 16 r 0000h fffb:a808 ctrl control and configuration register 16 rw 0000h fffb:a80c status status register 16 r 0000h fffb:a810 sync_cnt frame synchronization register 16 r undef fffb:a814 start_cnt frame start counter register 16 r undef functional overview 74 august 2002 ? revised august 2003 sprs197b 3.15.3 mpu configuration registers the mpu configuration registers include the following: ? pin multiplexing setup: ? omap5910 pin configuration registers ? local bus and mmu setup: ? local bus control registers ? local bus mmu registers ? dsp mmu registers ? mpui and tipb setup: ? mpu interface (mpui) registers ? tipb (private) bridge 1 configuration registers ? tipb (public) bridge 2 configuration registers ? mpu uart ti peripheral bus switch registers ? traffic controller registers ? clock and power management: ? mpu clock/reset/power mode control registers ? dpll1 configuration register ? ultra low-power device module registers ? device identification: ? device die identification registers ? jtag identification code register functional overview 75 august 2002 ? revised august 2003 sprs197b table 3?38. omap 5910 pin configuration registers byte address register name description access width access type reset value fffe:1000 func_mux_ctrl_0 functional multiplexing control 0 register 32 rw 0000 0000h fffe:1004 func_mux_ctrl_1 functional multiplexing control 1 register 32 rw 0000 0000h fffe:1008 func_mux_ctrl_2 functional multiplexing control 2 register 32 rw 0000 0000h fffe:100c comp_mode_ctrl_0 compatibility mode control 0 register 32 rw 0000 0000h fffe:1010 func_mux_ctrl_3 functional multiplexing control 3 register 32 rw 0000 0000h fffe:1014 func_mux_ctrl_4 functional multiplexing control 4 register 32 rw 0000 0000h fffe:1018 func_mux_ctrl_5 functional multiplexing control 5 register 32 rw 0000 0000h fffe:101c func_mux_ctrl_6 functional multiplexing control 6 register 32 rw 0000 0000h fffe:1020 func_mux_ctrl_7 functional multiplexing control 7 register 32 rw 0000 0000h fffe:1024 func_mux_ctrl_8 functional multiplexing control 8 register 32 rw 0000 0000h fffe:1028 func_mux_ctrl_9 functional multiplexing control 9 register 32 rw 0000 0000h fffe:102c func_mux_ctrl_a functional multiplexing control a register 32 rw 0000 0000h fffe:1030 func_mux_ctrl_b functional multiplexing control b register 32 rw 0000 0000h fffe:1034 func_mux_ctrl_c functional multiplexing control c register 32 rw 0000 0000h fffe:1038 func_mux_ctrl_d functional multiplexing control d register 32 rw 0000 0000h fffe:103c reserved fffe:1040 pull_dwn_ctrl_0 pulldown control 0 register 32 rw 0000 0000h fffe:1044 pull_dwn_ctrl_1 pulldown control 1 register 32 rw 0000 0000h fffe:1048 pull_dwn_ctrl_2 pulldown control 2 register 32 rw 0000 0000h fffe:104c pull_dwn_ctrl_3 pulldown control 3 register 32 rw 0000 0000h fffe:1050 gate_inh_ctrl_0 gate and inhibit control 0 register 32 rw 0000 0000h fffe:1054 ? fffe:105c reserved fffe:1060 voltage_ctrl_0 voltage control 0 register 32 rw 0000 0000h fffe:1064 ? fffe:106c reserved fffe:1070 test_dbg_ctrl_0 test debug control 0 register 32 rw 0000 0000h fffe:1074 ? fffe:107c reserved fffe:1080 mod_conf_ctrl_0 module configuration control 0 register 32 rw 0000 0000h table 3?39. local bus control registers byte address register name description access width access type reset value fffe:c100 lb_mpu_timeout local bus mpu access timeout 32 rw 0000 00ffh fffe:c104 lb_hold_timer local bus hold timer 32 rw 0000 0000h fffe:c108 lb_priority_reg local bus mpu access priority 32 rw 0000 0000h fffe:c10c lb_clock_div local bus clock divider 32 rw 0000 00fch fffe:c110 lb_abort_add local bus address of aborted mpu cycle 32 r ffff ffffh fffe:c114 lb_abort_data local bus cycle data of aborted mpu write cycle 32 r ffff ffffh fffe:c118 lb_abort_status local bus cycle type of aborted mpu write cycle 32 r 0000 0000h fffe:c11c lb_irq_output local bus external interrupt output control 32 rw 0000 0000h fffe:c120 lb_irq_input local bus external interrupt status 32 rw 0000 0000h functional overview 76 august 2002 ? revised august 2003 sprs197b table 3?40. local bus mmu registers byte address register name description access width access type reset value fffe:c204 lb_mmu_walking_st_reg local bus mmu walking status 32 rw ? 0000h fffe:c208 lb_mmu_cntl_reg local bus mmu control 32 rw ? 0000h fffe:c20c lb_mmu_fault_ad_h_reg local bus mmu fault address high 32 r 0000h fffe:c210 lb_mmu_fault_ad_l_reg local bus mmu fault address low 32 r 0000h fffe:c214 lb_mmu_fault_st_reg local bus mmu fault status 32 r 0000h fffe:c218 lb_mmu_it_ack_reg local bus mmu interrupt acknowledge 32 w 0000h fffe:c21c lb_mmu_ttb_h_reg local bus mmu ttb register high 32 rw ? 0000h fffe:c220 lb_mmu_ttb_l_reg local bus mmu ttb register low 32 rw ? 0000h fffe:c224 lb_mmu_lock_reg local bus mmu lock counter 32 rw 0000h fffe:c228 lb_mmu_ld_tlb_reg local bus mmu tlb load/read control 32 rw 0000h fffe:c22c lb_mmu_cam_h_reg local bus mmu cam entry high 32 rw 0000h fffe:c230 lb_mmu_cam_l_reg local bus mmu cam entry low 32 rw 0000h fffe:c234 lb_mmu_ram_h_reg local bus mmu ram entry high 32 rw 0000h fffe:c238 lb_mmu_ram_l_reg local bus mmu ram entry low 32 rw 0000h fffe:c23c lb_mmu_gflush_reg local bus mmu global flush control 32 rw 0000h fffe:c240 lb_mmu_flush_entry_reg local bus mmu individual entry flush control 32 rw 0000h fffe:c244 lb_mmu_read_cam_h_reg local bus mmu cam read high 32 rw 0000h fffe:c248 lb_mmu_read_cam_l_reg local bus mmu cam read low 32 rw 0000h fffe:c24c lb_mmu_read_ram_h_reg local bus mmu ram read high 32 rw 0000h fffe:c250 lb_mmu_read_ram_l_reg local bus mmu ram read low 32 rw 0000h ? write access in arm supervisor mode only. functional overview 77 august 2002 ? revised august 2003 sprs197b table 3?41. dsp mmu registers byte address register name description access width access type reset value fffe:d200 dsp_mmu_prefetch_reg dsp mmu prefetch register 32 rw 0000h fffe:d204 dsp_mmu_walking_st_reg dsp mmu prefetch status register 32 r 0000h fffe:d208 dsp_mmu_cntl_reg dsp mmu control register 32 rw 0000h fffe:d20c dsp_mmu_fault_ad_h_reg dsp mmu fault address register msb 32 r 0000h fffe:d210 dsp_mmu_fault_ad_l_reg dsp mmu fault address register lsb 32 r 0000h fffe:d214 dsp_mmu_f_st_reg dsp mmu fault status register 32 r 0000h fffe:d218 dsp_mmu_it_ack_reg dsp mmu it acknowledge register 32 w 0000h fffe:d21c dsp_mmu_ttb_h_reg dsp mmu ttb register msb 32 rw 0000h fffe:d220 dsp_mmu_ttb_l_reg dsp mmu ttb register lsb 32 rw 0000h fffe:d224 dsp_mmu_lock_reg dsp mmu lock counter register 32 rw 0000h fffe:d228 dsp_mmu_ld_tlb_reg dsp mmu load entry tlb register 32 rw 0000h fffe:d22c dsp_mmu_cam_h_reg dsp mmu cam entry register msb 32 rw 0000h fffe:d230 dsp_mmu_cam_l_reg dsp mmu cam entry register lsb 32 rw 0000h fffe:d234 dsp_mmu_ram_h_reg dsp mmu ram entry register msb 32 rw 0000h fffe:d238 dsp_mmu_ram_l_reg dsp mmu ram entry register lsb 32 rw 0000h fffe:d23c dsp_mmu_gflush_reg dsp mmu global flush register 32 rw 0000h fffe:d240 dsp_mmu_flush_entry_reg dsp mmu individual flush register 32 rw 0000h fffe:d244 dsp_mmu_read_cam_h_reg dsp mmu read cam register msb 32 rw 0000h fffe:d248 dsp_mmu_read_cam_l_reg dsp mmu read cam register lsb 32 rw 0000h fffe:d24c dsp_mmu_read_ram_h_reg dsp mmu read ram register msb 32 rw 0000h fffe:d250 dsp_mmu_read_ram_l_reg dsp mmu read ram register lsb 32 rw 0000h table 3?42. mpui registers byte address register name description access width access type reset value fffe:c900 ctrl_reg mpui control register 32 rw 0003 ff1bh fffe:c904 debug_addr mpui debug address register 32 r 01ff ffffh fffe:c908 debug_data mpui debug data register 32 r ffff ffffh fffe:c90c debug_flag mpui debug flag register 32 r 0800h fffe:c910 status_reg mpui status register 32 r 0000h fffe:c914 dsp_status_reg mpui dsp status register 32 r undef fffe:c918 dsp_boot_config mpui boot configuration register 32 rw 0000h fffe:c91c dsp_mpui_config mpui dsp mpui configuration register 32 rw ffffh table 3?43. tipb (private) bridge 1 configuration registers byte address register name description access width access type reset value fffe:ca00 tipb_cntl private tipb control register 32 rw ff11h fffe:ca04 tipb_bus_alloc private tipb bus allocation register 32 rw 0009h fffe:ca08 mpu_tipb_cntl private mpu tipb control register 32 rw 0000h fffe:ca0c enhanced_tipb_cntl private enhanced tipb control register 32 rw 0007h fffe:ca10 address_dbg private debug address register 32 r ffffh fffe:ca14 data_debug_low private debug data lsb register 32 r ffffh fffe:ca18 data_debug_high private debug data msb register 32 r ffffh fffe:ca1c debug_cntr_sig private debug control signals register 32 r 00f8h functional overview 78 august 2002 ? revised august 2003 sprs197b table 3?44. tipb (public) bridge 2 configuration registers byte address register name description access width access type reset value fffe:d300 tipb_cntl public tipb control register 16 rw ff11h fffe:d304 tipb_bus_alloc public tipb bus allocation register 16 rw 0009h fffe:d308 mpu_tipb_cntl public mpu tipb control register 16 rw 0000h fffe:d30c enhanced_tipb_cntl public enhanced tipb control register 16 rw 0007h fffe:d310 address_dbg public debug address register 16 r ffffh fffe:d314 data_debug_low public debug data lsb register 16 r ffffh fffe:d318 data_debug_high public debug data msb register 16 r ffffh fffe:d31c debug_cntr_sig public debug control signals register 16 r 00f8h table 3?45. mpu uart tipb bus switch registers byte address register name description access width access type reset value fffb:c800 rhsw_arm_cnf1 uart1 tipb switch configuration register (mpu) 16 rw 0001h fffb:c804 rhsw_arm_sta1 uart1 tipb switch status register (mpu) 16 r 0001h fffb:c808 ? fffb:c83c reserved fffb:c840 rhsw_arm_cnf2 uart2 tipb switch configuration register (mpu) 16 rw 0001h fffb:c844 rhsw_arm_sta2 uart2 tipb switch status register (mpu) 16 r 0001h fffb:c848 ? fffb:c87c reserved fffb:c880 rhsw_arm_cnf3 uart3 tipb switch configuration register (mpu) 16 rw 0001h fffb:c884 rhsw_arm_sta3 uart3 tipb switch status register (mpu) 16 r 0001h functional overview 79 august 2002 ? revised august 2003 sprs197b table 3?46. traffic controller registers byte address register name description access width access type reset value fffe:cc00 imif_prio tc imif priority register 32 rw 0000 0000h fffe:cc04 emifs_prio_reg tc emifs priority register 32 rw 0000 0000h fffe:cc08 emiff_prio_reg tc emiff priority register 32 rw 0000 0000h fffe:cc0c emifs_config_reg tc emifs configuration register 32 rw y00z0b ? fffe:cc10 emifs_cs0_config tc emifs cs0 configuration register 32 rw 0010 fffbh fffe:cc14 emifs_cs1_config tc emifs cs1 configuration register 32 rw 0010 fffbh fffe:cc18 emifs_cs2_config tc emifs cs2 configuration register 32 rw 0010 fffbh fffe:cc1c emifs_cs3_config tc emifs cs3 configuration register 32 rw 0010 fffbh fffe:cc20 emiff_sdram_config tc emiff sdram configuration register 32 rw 0061 8800h fffe:cc24 emiff_mrs tc emiff sdram mrs register 32 rw 0000 0037h fffe:cc28 timeout1 tc timeout 1 register 32 rw 0000 0000h fffe:cc2c timeout2 tc timeout 2 register 32 rw 0000 0000h fffe:cc30 timeout3 tc timeout 3 register 32 rw 0000 0000h fffe:cc34 endianism tc endianism register 32 rw 0000 0000h fffe:cc38 reserved 32 rw 0000 0000h fffe:cc3c emiff_sdram_config_2 tc emiff sdram configuration register 2 32 rw 0000 0003h fffe:cc40 emifs_cfg_dyn_wait tc emifs wait-state configuration register 32 rw 0000 0000h ? the value of y is dependent upon the state of the flash.rdy pin and the value of z is dependent upon the state of the mpu_boot pin upon power-on reset. table 3?47. mpu clock/reset/power mode control registers byte address register name description access width access type reset value fffe:ce00 arm_ckctl mpu clock control register 32 rw 3000h fffe:ce04 arm_idlect1 mpu idle control 1 register 32 rw 0400h fffe:ce08 arm_idlect2 mpu idle control 2 register 32 rw 0100h fffe:ce0c arm_ewupct mpu external wakeup control register 32 rw 003fh fffe:ce10 arm_rstct1 mpu reset control 1 register 32 rw 0000h fffe:ce14 arm_rstct2 mpu reset control 2 register 32 rw 0000h fffe:ce18 arm_sysst mpu system status register 32 rw 0038h table 3?48. dpll1 register byte address register name description access width access type reset value fffe:cf00 dpll1_ctl_reg dpll1 control register 32 rw 0000 2002h functional overview 80 august 2002 ? revised august 2003 sprs197b table 3?49. ultra low-power device module registers byte address register name description access width access type reset value fffe:0800 counter_32_lsb ulpd 32-khz counter register lsb 16 r 0001h fffe:0804 counter_32_msb ulpd 32-khz counter register msb 16 r 0001h fffe:0808 counter_high_freq_lsb ulpd high-frequency counter lsb register 16 r 0001h fffe:080c counter_high_freq_msb ulpd high-frequency counter msb register 16 r 0000h fffe:0810 gauging_ctrl_reg ulpd gauging control register 16 rw 0000h fffe:0814 it_status_reg ulpd interrupt status register 16 r 0000h fffe:0818 ? fffe:0820 reserved fffe:0824 setup_ulpd1_reg ulpd wakeup time setup register 16 rw 03ffh fffe:0828 ? fffe:082c reserved fffe:0830 clock_ctrl_reg ulpd clock control register 16 rw 0000h fffe:0834 soft_req_reg ulpd soft clock request register 16 rw 0000h fffe:0838 counter_32_fiq_reg ulpd modem shutdown delay register 16 rw 0001h fffe:083c dpll_ctrl_reg ulpd usb dpll control register 16 rw 2211h fffe:0840 status_req_reg ulpd hardware request status register 16 rw undef fffe:0844 reserved fffe:0848 lock_time_reg ulpd apll lock time register 16 rw 0960h fffe:084c apll_ctrl_reg ulpd apll control register 16 rw undef fffe:0850 power_ctrl_reg ulpd power control register 16 rw 0008h table 3?50. device die identification registers byte address register name description access width access type reset value fffe:1800 die_id_lsb device die identification register (lsb) 32 r ? fffe:1804 die_id_msb device die identification register (msb) 32 r ? table 3?51. jtag identification code register byte address register name description access width access type reset value fffe:d404 jtag_id jtag identification code register 32 r ? functional overview 81 august 2002 ? revised august 2003 sprs197b 3.16 dsp register descriptions the following tables describe the dsp registers including register addresses, descriptions, required access widths, access types (r-read, w-write, rw-read/write) and reset values. these tables are organized by function with like peripherals or functions together and are therefore not necessarily in the order of ascending register addresses. note: all accesses to these registers must be of the data access widths indicated to avoid a tipb bus error condition and a corresponding interrupt. reserved addresses should never be accessed 3.16.1 dsp private peripheral registers the dsp private peripheral registers include the following: ? dma controller: ? dsp dma controller registers ? timers: ? dsp timer 1 registers ? dsp timer 2 registers ? dsp timer 3 registers ? dsp watchdog timer registers ? interrupt control: ? dsp interrupt interface registers ? dsp level 2 interrupt handler registers functional overview 82 august 2002 ? revised august 2003 sprs197b table 3?52. dsp dma controller registers dsp word address register name description access width access type reset value 0x00 0c00h dma_csdp0 channel 0 source/destination parameters register 16 rw 0000h 0x00 0c01h dma_ccr0 channel 0 control register 16 rw 0000h 0x00 0c02h dma_cicr0 channel 0 interrupt control register 16 rw 0003h 0x00 0c03h dma_csr0 channel 0 status register 16 r 0000h 0x00 0c04h dma_cssa_l0 channel 0 source start address register lsb 16 rw undef 0x00 0c05h dma_cssa_u0 channel 0 source start address register msb 16 rw undef 0x00 0c06h dma_cdsa_l0 channel 0 destination start address register lsb 16 rw undef 0x00 0c07h dma_cdsa_u0 channel 0 destination start address register msb 16 rw undef 0x00 0c08h dma_cen0 channel 0 element number register 16 rw undef 0x00 0c09h dma_cfn0 channel 0 frame number register 16 rw undef 0x00 0c0ah dma_csfi0 channel 0 frame index register 16 rw undef 0x00 0c0bh dma_csei0 channel 0 element index register 16 rw undef 0x00 0c0ch dma_csac0 channel 0 source address counter register 16 rw undef 0x00 0c0dh dma_cdac0 channel 0 destination address counter register 16 rw undef 0x00 0c0eh dma_cdfi0 channel 0 destination frame index 16 rw undef 0x00 0c0fh dma_cdei0 channel 0 destination element index 16 rw undef 0x00 0c10h ? 0x00 0c1fh reserved 0x00 0c20h dma_csdp1 channel 1 source/destination parameters register 16 rw 0000h 0x00 0c21h dma_ccr1 channel 1 control register 16 rw 0000h 0x00 0c22h dma_cicr1 channel 1 interrupt control register 16 rw 0003h 0x00 0c23h dma_csr1 channel 1 status register 16 r 0000h 0x00 0c24h dma_cssa_l1 channel 1 source start address register lsb 16 rw undef 0x00 0c25h dma_cssa_u1 channel 1 source start address register msb 16 rw undef 0x00 0c26h dma_cdsa_l1 channel 1 destination start address register lsb 16 rw undef 0x00 0c27h dma_cdsa_u1 channel 1 destination start address register msb 16 rw undef 0x00 0c28h dma_cen1 channel 1 element number register 16 rw undef 0x00 0c29h dma_cfn1 channel 1 frame number register 16 rw undef 0x00 0c2ah dma_csfi1 channel 1 frame index register 16 rw undef 0x00 0c2bh dma_csei1 channel 1 element index register 16 rw undef 0x00 0c2ch dma_csac1 channel 1 source address counter register 16 rw undef 0x00 0c2dh dma_cdac1 channel 1 destination address counter register 16 rw undef 0x00 0c2eh dma_cdfi1 channel 1 destination frame index 16 rw undef 0x00 0c2fh dma_cdei1 channel 1 destination element index 16 rw undef 0x00 0c30h ? 0x00 0c3fh reserved 0x00 0c40h dma_csdp2 channel 2 source/destination parameters register 16 rw 0000h 0x00 0c41h dma_ccr2 channel 2 control register 16 rw 0000h 0x00 0c42h dma_cicr2 channel 2 interrupt control register 16 rw 0003h 0x00 0c43h dma_csr2 channel 2 status register 16 r 0000h 0x00 0c44h dma_cssa_l2 channel 2 source start address register lsb 16 rw undef 0x00 0c45h dma_cssa_u2 channel 2 source start address register msb 16 rw undef 0x00 0c46h dma_cdsa_l2 channel 2 destination start address register lsb 16 rw undef 0x00 0c47h dma_cdsa_u2 channel 2 destination start address register msb 16 rw undef functional overview 83 august 2002 ? revised august 2003 sprs197b table 3?52. dsp dma controller registers (continued) dsp word address reset value access type access width description register name 0x00 0c48h dma_cen2 channel 2 element number register 16 rw undef 0x00 0c49h dma_cfn2 channel 2 frame number register 16 rw undef 0x00 0c4ah dma_csfi2 channel 2 frame index register 16 rw undef 0x00 0c4bh dma_csei2 channel 2 element index register 16 rw undef 0x00 0c4ch dma_csac2 channel 2 source address counter register 16 rw undef 0x00 0c4dh dma_cdac2 channel 2 destination address counter register 16 rw undef 0x00 0c4eh dma_cdfi2 channel 2 destination frame index 16 rw undef 0x00 0c4fh dma_cdei2 channel 2 destination element index 16 rw undef 0x00 0c50h ? 0x00 0c5fh reserved 0x00 0c60h dma_csdp3 channel 3 source/destination parameters register 16 rw 0000h 0x00 0c61h dma_ccr3 channel 3 control register 16 rw 0000h 0x00 0c62h dma_cicr3 channel 3 interrupt control register 16 rw 0003h 0x00 0c63h dma_csr3 channel 3 status register 16 r 0000h 0x00 0c64h dma_cssa_l3 channel 3 source start address register lsb 16 rw undef 0x00 0c65h dma_cssa_u3 channel 3 source start address register msb 16 rw undef 0x00 0c66h dma_cdsa_l3 channel 3 destination start address register lsb 16 rw undef 0x00 0c67h dma_cdsa_u3 channel 3 destination start address register msb 16 rw undef 0x00 0c68h dma_cen3 channel 3 element number register 16 rw undef 0x00 0c69h dma_cfn3 channel 3 frame number register 16 rw undef 0x00 0c6ah dma_csfi3 channel 3 frame index register 16 rw undef 0x00 0c6bh dma_csei3 channel 3 element index register 16 rw undef 0x00 0c6ch dma_csac3 channel 3 source address counter register 16 rw undef 0x00 0c6dh dma_cdac3 channel 3 destination address counter register 16 rw undef 0x00 0c6eh dma_cdfi3 channel 3 destination frame index 16 rw undef 0x00 0c6fh dma_cdei3 channel 3 destination element index 16 rw undef 0x00 0c70h ? 0x00 0c7fh reserved 0x00 0c80h dma_csdp4 channel 4 source/destination parameters register 16 rw 0000h 0x00 0c81h dma_ccr4 channel 4 control register 16 rw 0000h 0x00 0c82h dma_cicr4 channel 4 interrupt control register 16 rw 0003h 0x00 0c83h dma_csr4 channel 4 status register 16 r 0000h 0x00 0c84h dma_cssa_l4 channel 4 source start address register lsb 16 rw undef 0x00 0c85h dma_cssa_u4 channel 4 source start address register msb 16 rw undef 0x00 0c86h dma_cdsa_l4 channel 4 destination start address register lsb 16 rw undef 0x00 0c87h dma_cdsa_u4 channel 4 destination start address register msb 16 rw undef 0x00 0c88h dma_cen4 channel 4 element number register 16 rw undef 0x00 0c89h dma_cfn4 channel 4 frame number register 16 rw undef 0x00 0c8ah dma_csfi4 channel 4 frame index register 16 rw undef 0x00 0c8bh dma_csei4 channel 4 element index register 16 rw undef 0x00 0c8ch dma_csac4 channel 4 source address counter register 16 rw undef 0x00 0c8dh dma_cdac4 channel 4 destination address counter register 16 rw undef 0x00 0c8eh dma_cdfi4 channel 4 destination frame index 16 rw undef 0x00 0c8fh dma_cdei4 channel 4 destination element index 16 rw undef functional overview 84 august 2002 ? revised august 2003 sprs197b table 3?52. dsp dma controller registers (continued) dsp word address reset value access type access width description register name 0x00 0c90h ? 0x00 0c9fh reserved 0x00 0ca0h dma_csdp5 channel 5 source/destination parameters register 16 rw 0000h 0x00 0ca1h dma_ccr5 channel 5 control register 16 rw 0000h 0x00 0ca2h dma_cicr5 channel 5 interrupt control register 16 rw 0003h 0x00 0ca3h dma_csr5 channel 5 status register 16 r 0000h 0x00 0ca4h dma_cssa_l5 channel 5 source start address register lsb 16 rw undef 0x00 0ca5h dma_cssa_u5 channel 5 source start address register msb 16 rw undef 0x00 0ca6h dma_cdsa_l5 channel 5 destination start address register lsb 16 rw undef 0x00 0ca7h dma_cdsa_u5 channel 5 destination start address register msb 16 rw undef 0x00 0ca8h dma_cen5 channel 5 element number register 16 rw undef 0x00 0ca9h dma_cfn5 channel 5 frame number register 16 rw undef 0x00 0caah dma_csfi5 channel 5 frame index register 16 rw undef 0x00 0cabh dma_csei5 channel 5 element index register 16 rw undef 0x00 0cach dma_csac5 channel 5 source address counter register 16 rw undef 0x00 0cadh dma_cdac5 channel 5 destination address counter register 16 rw undef 0x00 0caeh dma_cdfi5 channel 5 destination frame index 16 rw undef 0x00 0cafh dma_cdei5 channel 5 destination element index 16 rw undef 0x00 0cb0h ? 0x00 0dffh reserved 0x00 0e00h dma_gcr global control register 16 rw 0008h 0x00 0e01h dma_gtcr global timeout control register 16 rw 0000h 0x00 0e02h dma_gscr global software incompatible control register 16 rw 0000h functional overview 85 august 2002 ? revised august 2003 sprs197b table 3?53. dsp timer 1 registers dsp word address register name description access width access type reset value 0x00 2800h dsp_cntl_timer_1 dsp timer 1 control timer register 16 rw 0000h 0x00 2801h reserved 0x00 2802h dsp_load_tim_hi_1 dsp timer 1 load timer high register 16 w undef 0x00 2803h dsp_load_tim_lo_1 dsp timer 1 load timer low register 16 w undef 0x00 2804h dsp_read_tim_hi_1 dsp timer 1 read timer high register 16 r undef 0x00 2805h dsp_read_tim_lo_1 dsp timer 1 read timer low register 16 r undef table 3?54. dsp timer 2 registers dsp word address register name description access width access type reset value 0x00 2c00h dsp_cntl_timer_2 dsp timer 2 control timer register 16 rw 0000h 0x00 2c01h reserved 0x00 2c02h dsp_load_tim_hi_2 dsp timer 2 load timer high register 16 w undef 0x00 2c03h dsp_load_tim_lo_2 dsp timer 2 load timer low register 16 w undef 0x00 2c04h dsp_read_tim_hi_2 dsp timer 2 read timer high register 16 r undef 0x00 2c05h dsp_read_tim_lo_2 dsp timer 2 read timer low register 16 r undef table 3?55. dsp timer 3 registers dsp word address register name description access width access type reset value 0x00 3000h dsp_cntl_timer_3 dsp timer 3 control timer register 16 rw 0000h 0x00 3001h reserved 0x00 3002h dsp_load_tim_hi_3 dsp timer 3 load timer high register 16 w undef 0x00 3003h dsp_load_tim_lo_3 dsp timer 3 load timer low register 16 w undef 0x00 3004h dsp_read_tim_hi_3 dsp timer 3 read timer high register 16 r undef 0x00 3005h dsp_read_tim_lo_3 dsp timer 3 read timer low register 16 r undef table 3?56. dsp watchdog timer registers dsp word address register name description access width access type reset value 0x00 3400h dsp_cntl_timer_wd dsp wdt control timer register 16 rw 0002h 0x00 3401h reserved 0x00 3402h dsp_load_tim_wd dsp wdt load timer register 16 w ffffh 0x00 3402h dsp_read_tim_wd dsp wdt read timer register 16 r ffffh 0x00 3403h reserved 0x00 3404h dsp_timer_mode_wd dsp wdt timer mode register 16 rw 8000h table 3?57. dsp interrupt interface registers dsp word address register name description access width access type reset value 0x00 3800h et_ls_ctrl_hi edge triggered/level sensitive control register high 16 rw 0000h 0x00 3801h et_ls_ctrl_lo edge triggered/level sensitive control register low 16 rw 0000h 0x00 3802h rst_lvl_lo level sensitive clear low register 16 w 0000h 0x00 3803h rst_lvl_hi level sensitive clear high register 16 w 0000h functional overview 86 august 2002 ? revised august 2003 sprs197b table 3?58. dsp level 2 interrupt handler registers dsp word address register name description access width access type reset value 0x00 4800h dsp_l2_itr interrupt register 16 rw 0000h 0x00 4802h dsp_l2_mir mask interrupt register 16 rw ffffh 0x00 4804h dsp_l2_sir_irq_code irq interrupt encoded source register 16 r 0000h 0x00 4806h dsp_l2_sir_fiq_code fiq interrupt encoded source register 16 r 0000h 0x00 4808h dsp_l2_control_reg interrupt control register 16 rw 0000h 0x00 480ah dsp_l2_isr software interrupt set register 16 rw 0000h 0x00 480ch dsp_l2_ilr0 interrupt 0 priority level register 16 rw 0000h 0x00 480eh dsp_l2_ilr1 interrupt 1 priority level register 16 rw 0000h 0x00 4810h dsp_l2_ilr2 interrupt 2 priority level register 16 rw 0000h 0x00 4812h dsp_l2_ilr3 interrupt 3 priority level register 16 rw 0000h 0x00 4814h dsp_l2_ilr4 interrupt 4 priority level register 16 rw 0000h 0x00 4816h dsp_l2_ilr5 interrupt 5 priority level register 16 rw 0000h 0x00 4818h dsp_l2_ilr6 interrupt 6 priority level register 16 rw 0000h 0x00 481ah dsp_l2_ilr7 interrupt 7 priority level register 16 rw 0000h 0x00 481ch dsp_l2_ilr8 interrupt 8 priority level register 16 rw 0000h 0x00 481eh dsp_l2_ilr9 interrupt 9 priority level register 16 rw 0000h 0x00 4820h dsp_l2_ilr10 interrupt 10 priority level register 16 rw 0000h 0x00 4822h dsp_l2_ilr11 interrupt 11 priority level register 16 rw 0000h 0x00 4824h dsp_l2_ilr12 interrupt 12 priority level register 16 rw 0000h 0x00 4826h dsp_l2_ilr13 interrupt 13 priority level register 16 rw 0000h 0x00 4828h dsp_l2_ilr14 interrupt 14 priority level register 16 rw 0000h 0x00 482ah dsp_l2_ilr15 interrupt 15 priority level register 16 rw 0000h functional overview 87 august 2002 ? revised august 2003 sprs197b 3.16.2 dsp public peripheral registers the dsp public peripheral registers include the following: ? serial ports: ? mcbsp1 registers ? mcbsp3 registers ? mcsi1 registers ? mcsi2 registers table 3?59. mcbsp1 registers dsp word address mpu byte address (via mpui) register name description access width access type reset value 0x00 8c00h e101:1800 mcbsp1_drr2 mcbsp1 data receive register 2 16 rw 0000h 0x00 8c01h e101:1802 mcbsp1_drr1 mcbsp1 data receive register 1 16 rw 0000h 0x00 8c02h e101:1804 mcbsp1_dxr2 mcbsp1 data transmit register 2 16 rw 0000h 0x00 8c03h e101:1806 mcbsp1_dxr1 mcbsp1 data transmit register 1 16 rw 0000h 0x00 8c04h e101:1808 mcbsp1_spcr2 mcbsp1 serial port control register 2 16 rw 0000h 0x00 8c05h e101:180a mcbsp1_spcr1 mcbsp1 serial port control register 1 16 rw 0000h 0x00 8c06h e101:180c mcbsp1_rcr2 mcbsp1 receive control register 2 16 rw 0000h 0x00 8c07h e101:180e mcbsp1_rcr1 mcbsp1 receive control register 1 16 rw 0000h 0x00 8c08h e101:1810 mcbsp1_xcr2 mcbsp1 transmit control register 2 16 rw 0000h 0x00 8c09h e101:1812 mcbsp1_xcr1 mcbsp1 transmit control register 1 16 rw 0000h 0x00 8c0ah e101:1814 mcbsp1_srgr2 mcbsp1 sample rate generator register 2 16 rw 2000h 0x00 8c0bh e101:1816 mcbsp1_srgr1 mcbsp1 sample rate generator register 1 16 rw 0001h 0x00 8c0ch e101:1818 mcbsp1_mcr2 mcbsp1 multichannel register 2 16 rw 0000h 0x00 8c0dh e101:181a mcbsp1_mcr1 mcbsp1 multichannel register 1 16 rw 0000h 0x00 8c0eh e101:181c mcbsp1_rcera mcbsp1 receive channel enable register partition a 16 rw 0000h 0x00 8c0fh e101:181e mcbsp1_rcerb mcbsp1 receive channel enable register partition b 16 rw 0000h 0x00 8c10h e101:1820 mcbsp1_xcera mcbsp1 transmit channel enable register partition a 16 rw 0000h 0x00 8c11h e101:1822 mcbsp1_xcerb mcbsp1 transmit channel enable register partition b 16 rw 0000h 0x00 8c12h e101:1824 mcbsp1_pcr0 mcbsp1 pin control register 0 16 rw 0000h 0x00 8c13h e101:1826 mcbsp1_rcerc mcbsp1 receive channel enable register partition c 16 rw 0000h 0x00 8c14h e101:1828 mcbsp1_rcerd mcbsp1 receive channel enable register partition d 16 rw 0000h 0x00 8c15h e101:182a mcbsp1_xcerc mcbsp1 transmit channel enable register partition c 16 rw 0000h 0x00 8c16h e101:182c mcbsp1_xcerd mcbsp1 transmit channel enable register partition d 16 rw 0000h 0x00 8c17h e101:182e mcbsp1_rcere mcbsp1 receive channel enable register partition e 16 rw 0000h 0x00 8c18h e101:1830 mcbsp1_rcerf mcbsp1 receive channel enable register partition f 16 rw 0000h 0x00 8c19h e101:1832 mcbsp1_xcere mcbsp1 transmit channel enable register partition e 16 rw 0000h 0x00 8c1ah e101:1834 mcbsp1_xcerf mcbsp1 transmit channel enable register partition f 16 rw 0000h functional overview 88 august 2002 ? revised august 2003 sprs197b table 3?59. mcbsp1 registers (continued) dsp word address reset value access type access width description register name mpu byte address (via mpui) 0x00 8c1bh e101:1836 mcbsp1_rcerg mcbsp1 receive channel enable register partition g 16 rw 0000h 0x00 8c1ch e101:1838 mcbsp1_rcerh mcbsp1 receive channel enable register partition h 16 rw 0000h 0x00 8c1dh e101:183a mcbsp1_xcerg mcbsp1 transmit channel enable register partition g 16 rw 0000h 0x00 8c1eh e101:183c mcbsp1_xcerh mcbsp1 transmit channel enable register partition h 16 rw 0000h table 3?60. mcbsp3 registers dsp word address mpu byte address (via mpui) register name description access width access type reset value 0x00 b800h e101:7000 mcbsp3_drr2 mcbsp3 data receive register 2 16 rw 0000h 0x00 b801h e101:7002 mcbsp3_drr1 mcbsp3 data receive register 1 16 rw 0000h 0x00 b802h e101:7004 mcbsp3_dxr2 mcbsp3 data transmit register 2 16 rw 0000h 0x00 b803h e101:7006 mcbsp3_dxr1 mcbsp3 data transmit register 1 16 rw 0000h 0x00 b804h e101:7008 mcbsp3_spcr2 mcbsp3 serial port control register 2 16 rw 0000h 0x00 b805h e101:700a mcbsp3_spcr1 mcbsp3 serial port control register 1 16 rw 0000h 0x00 b806h e101:700c mcbsp3_rcr2 mcbsp3 receive control register 2 16 rw 0000h 0x00 b807h e101:700e mcbsp3_rcr1 mcbsp3 receive control register 1 16 rw 0000h 0x00 b808h e101:7010 mcbsp3_xcr2 mcbsp3 transmit control register 2 16 rw 0000h 0x00 b809h e101:7012 mcbsp3_xcr1 mcbsp3 transmit control register 1 16 rw 0000h 0x00 b80ah e101:7014 mcbsp3_srgr2 mcbsp3 sample rate generator register 2 16 rw 2000h 0x00 b80bh e101:7016 mcbsp3_srgr1 mcbsp3 sample rate generator register 1 16 rw 0001h 0x00 b80ch e101:7018 mcbsp3_mcr2 mcbsp3 multichannel register 2 16 rw 0000h 0x00 b80dh e101:701a mcbsp3_mcr1 mcbsp3 multichannel register 1 16 rw 0000h 0x00 b80eh e101:701c mcbsp3_rcera mcbsp3 receive channel enable register partition a 16 rw 0000h 0x00 b80fh e101:701e mcbsp3_rcerb mcbsp3 receive channel enable register partition b 16 rw 0000h 0x00 b810h e101:7020 mcbsp3_xcera mcbsp3 transmit channel enable register partition a 16 rw 0000h 0x00 b811h e101:7022 mcbsp3_xcerb mcbsp3 transmit channel enable register partition b 16 rw 0000h 0x00 b812h e101:7024 mcbsp3_pcr0 mcbsp3 pin control register 0 16 rw 0000h 0x00 b813h e101:7026 mcbsp3_rcerc mcbsp3 receive channel enable register partition c 16 rw 0000h 0x00 b814h e101:7028 mcbsp3_rcerd mcbsp3 receive channel enable register partition d 16 rw 0000h 0x00 b815h e101:702a mcbsp3_xcerc mcbsp3 transmit channel enable register partition c 16 rw 0000h 0x00 b816h e101:702c mcbsp3_xcerd mcbsp3 transmit channel enable register partition d 16 rw 0000h 0x00 b817h e101:702e mcbsp3_rcere mcbsp3 receive channel enable register partition e 16 rw 0000h 0x00 b818h e101:7030 mcbsp3_rcerf mcbsp3 receive channel enable register partition f 16 rw 0000h functional overview 89 august 2002 ? revised august 2003 sprs197b table 3?60. mcbsp3 registers (continued) dsp word address reset value access type access width description register name mpu byte address (via mpui) 0x00 b819h e101:7032 mcbsp3_xcere mcbsp3 transmit channel enable register partition e 16 rw 0000h 0x00 b81ah e101:7034 mcbsp3_xcerf mcbsp3 transmit channel enable register partition f 16 rw 0000h 0x00 b81bh e101:7036 mcbsp3_rcerg mcbsp3 receive channel enable register partition g 16 rw 0000h 0x00 b81ch e101:7038 mcbsp3_rcerh mcbsp3 receive channel enable register partition h 16 rw 0000h 0x00 b81dh e101:703a mcbsp3_xcerg mcbsp3 transmit channel enable register partition g 16 rw 0000h 0x00 b81eh e101:703c mcbsp3_xcerh mcbsp3 transmit channel enable register partition h 16 rw 0000h functional overview 90 august 2002 ? revised august 2003 sprs197b table 3?61. mcsi1 registers dsp word address mpu byte address (via mpui) register name description access width access type reset value 0x00 9400h e101:2800 mcsi1_control_reg mcsi1 control register 16 rw 0000h 0x00 9401h e101:2802 mcsi1_main_parameters_reg mcsi1 main parameters register 16 rw 0000h 0x00 9402h e101:2804 mcsi1_interrupts_reg mcsi1 interrupts register 16 rw 0000h 0x00 9403h e101:2806 mcsi1_channel_used_reg mcsi1 channel used register 16 rw 0000h 0x00 9404h e101:2808 mcsi1_over_clock_reg mcsi1 over-clock register 16 rw 0000h 0x00 9405h e101:280a mcsi1_clock_frequency_ reg mcsi1 clock frequency register 16 rw 0000h 0x00 9406h e101:280c mcsi1_status_reg mcsi1 status register 16 rw 0000h 0x00 9407h? 0x00 941fh reserved 0x00 9420h e101:2840 mcsi1_tx0 mcsi1 transmit word register 0 16 rw undefined 0x00 9421h e101:2842 mcsi1_tx1 mcsi1 transmit word register 1 16 rw undefined 0x00 9422h e101:2844 mcsi1_tx2 mcsi1 transmit word register 2 16 rw undefined 0x00 9423h e101:2846 mcsi1_tx3 mcsi1 transmit word register 3 16 rw undefined 0x00 9424h e101:2848 mcsi1_tx4 mcsi1 transmit word register 4 16 rw undefined 0x00 9425h e101:284a mcsi1_tx5 mcsi1 transmit word register 5 16 rw undefined 0x00 9426h e101:284c mcsi1_tx6 mcsi1 transmit word register 6 16 rw undefined 0x00 9427h e101:284e mcsi1_tx7 mcsi1 transmit word register 7 16 rw undefined 0x00 9428h e101:2850 mcsi1_tx8 mcsi1 transmit word register 8 16 rw undefined 0x00 9429h e101:2852 mcsi1_tx9 mcsi1 transmit word register 9 16 rw undefined 0x00 942ah e101:2854 mcsi1_tx10 mcsi1 transmit word register 10 16 rw undefined 0x00 942bh e101:2856 mcsi1_tx11 mcsi1 transmit word register 11 16 rw undefined 0x00 942ch e101:2858 mcsi1_tx12 mcsi1 transmit word register 12 16 rw undefined 0x00 942dh e101:285a mcsi1_tx13 mcsi1 transmit word register 13 16 rw undefined 0x00 942eh e101:285c mcsi1_tx14 mcsi1 transmit word register 14 16 rw undefined 0x00 942fh e101:285e mcsi1_tx15 mcsi1 transmit word register 15 16 rw undefined 0x00 9430h e101:2860 mcsi1_rx0 mcsi1 receive word register 0 16 r undefined 0x00 9431h e101:2862 mcsi1_rx1 mcsi1 receive word register 1 16 r undefined 0x00 9432h e101:2864 mcsi1_rx2 mcsi1 receive word register 2 16 r undefined 0x00 9433h e101:2866 mcsi1_rx3 mcsi1 receive word register 3 16 r undefined 0x00 9434h e101:2868 mcsi1_rx4 mcsi1 receive word register 4 16 r undefined 0x00 9435h e101:286a mcsi1_rx5 mcsi1 receive word register 5 16 r undefined 0x00 9436h e101:286c mcsi1_rx6 mcsi1 receive word register 6 16 r undefined 0x00 9437h e101:286e mcsi1_rx7 mcsi1 receive word register 7 16 r undefined 0x00 9438h e101:2870 mcsi1_rx8 mcsi1 receive word register 8 16 r undefined 0x00 9439h e101:2872 mcsi1_rx9 mcsi1 receive word register 9 16 r undefined 0x00 943ah e101:2874 mcsi1_rx10 mcsi1 receive word register 10 16 r undefined 0x00 943bh e101:2876 mcsi1_rx11 mcsi1 receive word register 11 16 r undefined 0x00 943ch e101:2878 mcsi1_rx12 mcsi1 receive word register 12 16 r undefined 0x00 943dh e101:287a mcsi1_rx13 mcsi1 receive word register 13 16 r undefined 0x00 943eh e101:287c mcsi1_rx14 mcsi1 receive word register 14 16 r undefined 0x00 943fh e101:287e mcsi1_rx15 mcsi1 receive word register 15 16 r undefined functional overview 91 august 2002 ? revised august 2003 sprs197b table 3?62. mcsi2 registers dsp word address mpu byte address (via mpui) register name description access width access type reset value 0x00 9000h e101:2000 mcsi2_control_reg mcsi2 control register 16 rw 0000h 0x00 9001h e101:2002 mcsi2_main_parameters_reg mcsi2 main parameters register 16 rw 0000h 0x00 9002h e101:2004 mcsi2_interrupts_reg mcsi2 interrupts register 16 rw 0000h 0x00 9003h e101:2006 mcsi2_channel_used_reg mcsi2 channel used register 16 rw 0000h 0x00 9004h e101:2008 mcsi2_over_clock_reg mcsi2 over-clock register 16 rw 0000h 0x00 9005h e101:200a mcsi2_clock_frequency_ reg mcsi2 clock frequency register 16 rw 0000h 0x00 9006h e101:200c mcsi2_status_reg mcsi2 status register 16 rw 0000h 0x00 9007h ? 0x00 901fh reserved 0x00 9020h e101:2040 mcsi2_tx0 mcsi2 transmit word register 0 16 rw undefined 0x00 9021h e101:2042 mcsi2_tx1 mcsi2 transmit word register 1 16 rw undefined 0x00 9022h e101:2044 mcsi2_tx2 mcsi2 transmit word register 2 16 rw undefined 0x00 9023h e101:2046 mcsi2_tx3 mcsi2 transmit word register 3 16 rw undefined 0x00 9024h e101:2048 mcsi2_tx4 mcsi2 transmit word register 4 16 rw undefined 0x00 9025h e101:204a mcsi2_tx5 mcsi2 transmit word register 5 16 rw undefined 0x00 9026h e101:204c mcsi2_tx6 mcsi2 transmit word register 6 16 rw undefined 0x00 9027h e101:204e mcsi2_tx7 mcsi2 transmit word register 7 16 rw undefined 0x00 9028h e101:2050 mcsi2_tx8 mcsi2 transmit word register 8 16 rw undefined 0x00 9029h e101:2052 mcsi2_tx9 mcsi2 transmit word register 9 16 rw undefined 0x00 902ah e101:2054 mcsi2_tx10 mcsi2 transmit word register 10 16 rw undefined 0x00 902bh e101:2056 mcsi2_tx11 mcsi2 transmit word register 11 16 rw undefined 0x00 902ch e101:2058 mcsi2_tx12 mcsi2 transmit word register 12 16 rw undefined 0x00 902dh e101:205a mcsi2_tx13 mcsi2 transmit word register 13 16 rw undefined 0x00 902eh e101:205c mcsi2_tx14 mcsi2 transmit word register 14 16 rw undefined 0x00 902fh e101:205e mcsi2_tx15 mcsi2 transmit word register 15 16 rw undefined 0x00 9030h e101:2060 mcsi2_rx0 mcsi2 receive word register 0 16 r undefined 0x00 9031h e101:2062 mcsi2_rx1 mcsi2 receive word register 1 16 r undefined 0x00 9032h e101:2064 mcsi2_rx2 mcsi2 receive word register 2 16 r undefined 0x00 9033h e101:2066 mcsi2_rx3 mcsi2 receive word register 3 16 r undefined 0x00 9034h e101:2068 mcsi2_rx4 mcsi2 receive word register 4 16 r undefined 0x00 9035h e101:206a mcsi2_rx5 mcsi2 receive word register 5 16 r undefined 0x00 9036h e101:206c mcsi2_rx6 mcsi2 receive word register 6 16 r undefined 0x00 9037h e101:206e mcsi2_rx7 mcsi2 receive word register 7 16 r undefined 0x00 9038h e101:2070 mcsi2_rx8 mcsi2 receive word register 8 16 r undefined 0x00 9039h e101:2072 mcsi2_rx9 mcsi2 receive word register 9 16 r undefined 0x00 903ah e101:2074 mcsi2_rx10 mcsi2 receive word register 10 16 r undefined 0x00 903bh e101:2076 mcsi2_rx11 mcsi2 receive word register 11 16 r undefined 0x00 903ch e101:2078 mcsi2_rx12 mcsi2 receive word register 12 16 r undefined 0x00 903dh e101:207a mcsi2_rx13 mcsi2 receive word register 13 16 r undefined 0x00 903eh e101:207c mcsi2_rx14 mcsi2 receive word register 14 16 r undefined 0x00 903fh e101:207e mcsi2_rx15 mcsi2 receive word register 15 16 r undefined functional overview 92 august 2002 ? revised august 2003 sprs197b 3.16.3 dsp configuration registers the dsp configuration registers include the following: ? i-cache and emif setup ? dsp instruction cache registers ? dsp emif configuration registers ? tipb setup ? dsp tipb bridge configuration registers ? dsp uart ti peripheral bus switch registers ? clock control: ? dsp clock mode registers table 3?63. dsp instruction cache registers dsp word address register name description access width access type reset value 0x00 1400h icgc i-cache global control register 16 rw c006h 0x00 1401h reserved 16 rw 0000h 0x00 1402h reserved 16 rw 0000h 0x00 1403h icwc i-cache way control register 16 rw 000dh 0x00 1404h icst i-cache status register 16 r 0000h 0x00 1405h icrc1 i-cache ramset 1 control register 16 rw 000dh 0x00 1406h icrtag1 i-cache remset 1 tag register 16 rw 0000h 0x00 1407h icrc2 i-cache ramset 2 control register 16 rw 000dh 0x00 1408h icrtag2 i-cache remset 2 tag register 16 rw 0000h table 3?64. dsp emif configuration register dsp word address register name description access width access type reset value 0x00 0800h dsp_emif_gcr dsp emif global control register 16 rw 0020h 0x00 0801h dsp_emif_grr dsp emif global reset register 16 rw undef table 3?65. dsp tipb bridge configuration registers dsp word address register name description access width access type reset value 0x00 0000h tipb_cmr dsp tipb bridge control mode register 16 rw fe4dh 0x00 0001h tipb_icr dsp tipb bridge idle control register 16 rw 0000h 0x00 0002h tipb_istr dsp tipb bridge idle status register 16 r 0000h functional overview 93 august 2002 ? revised august 2003 sprs197b table 3?66. dsp uart tipb bus switch registers dsp word address register name description access width access type reset value 0x00 e400h rhsw_dsp_cnf1 uart1 tipb switch configuration register (dsp) 16 rw 0001h 0x00 e402h rhsw_dsp_sta1 uart1 tipb switch status register (dsp) 16 r 0001h 0x00 e404? 0x00 e0eh reserved 0x00 e410h rhsw_dsp_cnf2 uart2 tipb switch configuration register (dsp) 16 rw 0001h 0x00 e412h rhsw_dsp_sta2 uart2 tipb switch status register (dsp) 16 r 0001h 0x00 e414? 0x00 e1eh reserved 0x00 e420h rhsw_dsp_cnf3 uart3 tipb switch configuration register (dsp) 16 rw 0001h 0x00 e422h rhsw_dsp_sta3 uart3 tipb switch status register (dsp) 16 r 0001h table 3?67. dsp clock mode registers dsp word address mpu byte address (via mpui) register name description access width access type reset value 0x00 4000h e100:8000 dsp_ckctl dsp clock control register 16 rw 0000h 0x00 4002h e100:8004 dsp_idlect1 dsp idle control 1 register 16 rw 0000h 0x00 4004h e100:8008 dsp_idlect2 dsp idle control 2 register 16 rw 0000h 0x00 4006h ? 0x00 4008h reserved 0x00 400ah e100:8014 dsp_rstct2 dsp peripheral reset control register 16 rw 0000h 0x00 400ch e100:8018 dsp_sysst dsp system status register 16 rw 0000h functional overview 94 august 2002 ? revised august 2003 sprs197b 3.16.4 mpu/dsp shared peripheral register descriptions the following tables describe the mpu/dsp shared peripheral registers including register addresses, descriptions, required access widths, access types (r-read, w-write, rw-read/write) and reset values. these tables are organized by function with like peripherals or functions together and are therefore not necessarily in order of ascending register addresses. reserved addresses should never be accessed. note: all accesses to these registers must be of the data access widths indicated to avoid a tipb bus error condition and a corresponding interrupt. reserved addresses should never be accessed. the mpu/dsp shared peripheral registers include the following: ? uarts: ? uart1 registers ? uart2 registers ? uart3/irda registers ? gpio and mailboxes ? mpu/dsp shared gpio registers ? mpu/dsp shared mailbox registers functional overview 95 august 2002 ? revised august 2003 sprs197b table 3?68. uart1 registers dsp word address mpu byte address mpu byte address (via mpui) register name description access width access type reset value 0x00 8000h fffb:0000 e101:0000 uart1_rhr ? uart1 receive holding register 8 r undefined 0x00 8000h fffb:0000 e101:0000 uart1_thr ? uart1 transmit holding register 8 w undefined 0x00 8000h fffb:0000 e101:0000 uart1_dll ? uart1 divisor latch low register 8 rw 00h 0x00 8001h fffb:0004 e101:0002 uart1_ier ? uart1 interrupt enable register 8 rw 00h 0x00 8001h fffb:0004 e101:0002 uart1_dlh ? uart1 divisor latch high register 8 rw 00h 0x00 8002h fffb:0008 e101:0004 uart1_iir ?? uart1 interrupt identification register 8 r 01h 0x00 8002h fffb:0008 e101:0004 uart1_fcr ??? uart1 fifo control register 8 w 00h 0x00 8002h fffb:0008 e101:0004 uart1_efr uart1 enhanced feature register 8 rw 00h 0x00 8003h fffb:000c e101:0006 uart1_lcr uart1 line control register 8 rw 00h 0x00 8004h fffb:0010 e101:0008 uart1_mcr ??? uart1 modem control register 8 rw 00h 0x00 8004h fffb:0010 e101:0008 uart1_xon1 uart1 xon1 register 8 rw 00h 0x00 8005h fffb:0014 e101:000a uart1_lsr ?? uart1 mode register 8 r 60h 0x00 8005h fffb:0014 e101:000a uart1_xon2 uart1 xon2 register 8 rw 00h 0x00 8006h fffb:0018 e101:000c uart1_msr ?? uart1 modem status register 8 r undefined 0x00 8006h fffb:0018 e101:000c uart1_tcr # uart1 transmission control register 8 rw 0fh 0x00 8006h fffb:0018 e101:000c uart1_xoff1 uart1 xoff1 register 8 rw 00h 0x00 8007h fffb:001c e101:000e uart1_spr ?? uart1 scratchpad register 8 rw 00h 0x00 8007h fffb:001c e101:000e uart1_tlr # uart1 trigger level register 8 rw 00h 0x00 8007h fffb:001c e101:000e uart1_xoff2 uart1 xoff2 register 8 rw 00h 0x00 8008h fffb:0020 e101:0010 uart1_mdr1 uart1 mode definition 1 register 8 rw 07h 0x00 8009h ? 0x00 800dh fffb:0024 ? fffb:0034 reserved 0x00 800eh fffb:0038 e101:001c uart1_uasr ? uart1 autobauding status register 8 r 00h 0x00 800fh fffb:003c reserved 0x00 8010h fffb:0040 e101:0020 uart1_scr uart1 supplementary control register 8 rw 00h 0x00 8011h fffb:0044 e101:0022 uart1_ssr uart1 supplementary status register 8 r 00h 0x00 8012h fffb:0048 reserved 0x00 8013h fffb:004c e101:0026 uart1_osc_ 12m_sel ? uart1 12-/13-mhz oscillator select register 8 w 00h 0x00 8014h fffb:0050 e101:0028 uart1_mvr uart1 module version register 8 r ? ? register is accessible when lcr[7] = 0 (normal operating mode) ? register is accessible when lcr[7] = 1 and lcr[7:0] 0bfh register is accessible when lcr[7] = 0bfh ? register is write accessible when efr[4] = 1 # register is accessible when efr[4] = 1 and mcr[6] = 1 functional overview 96 august 2002 ? revised august 2003 sprs197b table 3?69. uart2 registers dsp word address mpu byte address mpu byte address (via mpui) register name description access width access type reset value 0x00 8400h fffb:0800 e101:0800 uart2_rhr ? uart2 receive holding register 8 r undefined 0x00 8400h fffb:0800 e101:0800 uart2_thr ? uart2 transmit holding register 8 w undefined 0x00 8400h fffb:0800 e101:0800 uart2_dll ? uart2 divisor latch low register 8 rw 00h 0x00 8401h fffb:0804 e101:0802 uart2_ier ? uart2 interrupt enable register 8 rw 00h 0x00 8401h fffb:0804 e101:0802 uart2_dlh ? uart2 divisor latch high register 8 rw 00h 0x00 8402h fffb:0808 e101:0804 uart2_iir ?? uart2 interrupt identification register 8 r 01h 0x00 8402h fffb:0808 e101:0804 uart2_fcr ??? uart2 fifo control register 8 w 00h 0x00 8402h fffb:0808 e101:0804 uart2_efr uart2 enhanced feature register 8 rw 00h 0x00 8403h fffb:080c e101:0806 uart2_lcr uart2 line control register 8 rw 00h 0x00 8404h fffb:0810 e101:0808 uart2_mcr ??? uart2 modem control register 8 rw 00h 0x00 8404h fffb:0810 e101:0808 uart2_xon1 uart2 xon1 register 8 rw 00h 0x00 8405h fffb:0814 e101:080a uart2_lsr ?? uart2 mode register 8 r 60h 0x00 8405h fffb:0814 e101:080a uart2_xon2 uart2 xon2 register 8 rw 00h 0x00 8406h fffb:0818 e101:080c uart2_msr ?? uart2 modem status register 8 r undefined 0x00 8406h fffb:0818 e101:080c uart2_tcr # uart2 transmission control register 8 rw 0fh 0x00 8406h fffb:0818 e101:080c uart2_xoff1 uart2 xoff1 register 8 rw 00h 0x00 8407h fffb:081c e101:080e uart2_spr ?? uart2 scratchpad register 8 rw 00h 0x00 8407h fffb:081c e101:080e uart2_tlr # uart2 trigger level register 8 rw 00h 0x00 8407h fffb:081c e101:080e uart2_xoff2 uart2 xoff2 register 8 rw 00h 0x00 8408h fffb:0820 e101:0810 uart2_mdr1 uart2 mode definition 1 register 8 rw 07h 0x00 8409 ? 0x00840dh fffb:0824 ? fffb:0834 reserved 0x00 840eh fffb:0838 e101:081c uart2_uasr ? uart2 autobauding status register 8 r 00h 0x00 840fh fffb:083c reserved 0x00 8410h fffb:0840 e101:0820 uart2_scr uart2 supplementary control register 8 rw 00h 0x00 8411h fffb:0844 e101:0822 uart2_ssr uart2 supplementary status register 8 r 00h 0x00 8412h fffb:0848 reserved 0x00 8413h fffb:084c e101:0826 uart2_osc_ 12m_selv ? uart2 12-/13-mhz oscillator select register 8 w 00h 0x00 8414h fffb:0850 e101:0828 uart2_mvr uart2 module version register 8 r ? ? register is accessible when lcr[7] = 0 (normal operating mode) ? register is accessible when lcr[7] = 1 and lcr[7:0] 0bfh register is accessible when lcr[7] = 0bfh ? register is write accessible when efr[4] = 1 # register is accessible when efr[4] = 1 and mcr[6] = 1 functional overview 97 august 2002 ? revised august 2003 sprs197b table 3?70. uart3/irda registers dsp word address mpu byte address mpu byte address (via mpui) register name description access width access type reset value 0x00 cc00h fffb:9800 e101:9800 uart3_rhr ? uart3 receive holding register 8 r undefined 0x00 cc00h fffb:9800 e101:9800 uart3_thr ? uart3 transmit holding register 8 w undefined 0x00 cc00h fffb:9800 e101:9800 uart3_dll ? uart3 divisor latch low register 8 rw 00h 0x00 cc01h fffb:9804 e101:9802 uart3_ier ? uart3 interrupt enable register 8 rw 00h 0x00 cc01h fffb:9804 e101:9802 uart3_dlh ? uart3 divisor latch high register 8 rw 00h 0x00 cc02h fffb:9808 e101:9804 uart3_iir ?? uart3 interrupt identification register 8 r 01h 0x00 cc02h fffb:9808 e101:9804 uart3_fcr ??? uart3 fifo control register 8 w 00h 0x00 cc02h fffb:9808 e101:9804 uart3_efr uart3 enhanced feature register 8 rw 00h 0x00 cc03h fffb:980c e101:9806 uart3_lcr uart3 line control register 8 rw 00h 0x00 cc04h fffb:9810 e101:9808 uart3_mcr ??? uart3 modem control register 8 rw 00h 0x00 cc04h fffb:9810 e101:9808 uart3_xon1 uart3 xon1 register 8 rw 00h 0x00 cc05h fffb:9814 e101:980a uart3_lsr ?? uart3 mode register 8 r 60h 0x00 cc05h fffb:9814 e101:980a uart3_xon2 uart3 xon2 register 8 rw 00h 0x00 cc06h fffb:9818 e101:980c uart3_msr ?? uart3 modem status register 8 r undefined 0x00 cc06h fffb:9818 e101:980c uart3_tcr # uart3 transmission control register 8 rw 0fh 0x00 cc06h fffb:9818 e101:980c uart3_xoff1 uart3 xoff1 register 8 rw 00h 0x00 cc07h fffb:981c e101:980e uart3_spr ?? uart3 scratchpad register 8 rw 00h 0x00 cc07h fffb:981c e101:980e uart3_tlr # uart3 trigger level register 8 rw 00h 0x00 cc07h fffb:981c e101:980e uart3_xoff2 uart3 xoff2 register 8 rw 00h 0x00 cc08h fffb:9820 e101:9810 uart3_mdr1 uart3 mode definition 1 register 8 rw 07h 0x00 cc09h fffb:9824 e101:9812 uart3_mdr2 uart3 mode definition register 2 8 rw 00h 0x00 cc0ah fffb:9828 e101:9814 uart3_sflsr uart3 status fifo line status register 8 r 00h 0x00 cc0ah fffb:9828 e101:9814 uart3_txfll uart3 transmit frame length low 8 w 00h 0x00 cc0bh fffb:982c e101:9816 uart3_resume uart3 resume register 8 r 00h 0x00 cc0bh fffb:982c e101:9816 uart3_txflh uart3 transmit frame length high 8 w 00h 0x00 cc0ch fffb:9830 e101:9818 uart3_sfregl uart3 status fifo low register 8 r undefined 0x00 cc0ch fffb:9830 e101:9818 uart3_rxfll uart3 receive frame length low 8 w 00h 0x00 cc0dh fffb:9834 e101:981a uart3_sfregh uart3 status fifo high register 8 r undefined 0x00 cc0dh fffb:9834 e101:981a uart3_rxflh uart3 receive frame length high 8 w 00h 0x00 cc0eh fffb:9838 e101:981c uart3_blr ? uart3 bof control register 8 rw 40h 0x00 cc0fh fffb:983c e101:981e uart3_acreg ? uart3 auxiliary control register 8 rw 00h 0x00 cc0fh fffb:983c e101:981e uart3_div16 ? uart3 divide 1.6 register 8 rw 00h 0x00 cc10h fffb:9840 e101:9820 uart3_scr uart3 supplementary control register 8 rw 00h ? register is accessible when lcr[7] = 0 (normal operating mode) ? register is accessible when lcr[7] = 1 and lcr[7:0] 0bfh register is accessible when lcr[7] = 0bfh ? register is write accessible when efr[4] = 1 # register is accessible when efr[4] = 1 and mcr[6] = 1 functional overview 98 august 2002 ? revised august 2003 sprs197b table 3?71. mpu/dsp shared gpio registers dsp word address mpu byte address register name description access width mpu access dsp access reset value 0x00 f000h fffc:e000 data_input data input register 16 r r 0000h 0x00 f002h fffc:e004 data_output data output register 16 rw rw ffffh 0x00 f004h fffc:e008 direction_control direction control register 16 rw rw ffffh 0x00 f006h fffc:e00c interrupt_control interrupt control register 16 rw rw ffffh 0x00 f008h fffc:e010 interrupt_mask interrupt mask register 16 rw rw ffffh 0x00 f00ah fffc:e014 interrupt_status interrupt status register 16 rw rw 0000h 0x00 f00ch fffc:e018 pin_control pin control register 16 rw r ffffh table 3?72. mpu/dsp shared mailbox registers dsp word address mpu byte address register name description access width mpu access type dsp access type reset value 0x00 f800h fffc:f000 arm2dsp1 mpu to dsp 1 data register 16 rw r 0000h 0x00 f802h fffc:f004 arm2dsp1b mpu to dsp 1 command register 16 rw r 0000h 0x00 f804h fffc:f008 dsp2arm1 dsp to mpu 1 data register 16 r rw 0000h 0x00 f806h fffc:f00c dsp2arm1b dsp to mpu 1 command register 16 r rw 0000h 0x00 f808h fffc:f010 dsp2arm2 dsp to mpu 2 data register 16 r rw 0000h 0x00 f80ah fffc:f014 dsp2arm2b dsp to mpu 2 command register 16 r rw 0000h 0x00 f80ch fffc:f018 arm2dsp1_flag mpu to dsp 1 flag register 16 r r undef 0x00 f80eh fffc:f01c dsp2arm1_flag dsp to mpu 1 flag register 16 r r undef 0x00 f810h fffc:f020 dsp2arm2_flag dsp to mpu 2 flag register 16 r r undef 0x00 f812h fffc:f024 arm2dsp2 mpu to dsp 2 data register 16 rw r 0000h 0x00 f814h fffc:f028 arm2dsp2b mpu to dsp 2 command register 16 rw r 0000h 0x00 f816h fffc:f02c arm2dsp2_flag mpu to dsp 2 flag register 16 r r undef functional overview 99 august 2002 ? revised august 2003 sprs197b 3.17 interrupts table 3?73. mpu level 1 and level 2 interrupt mappings interrupt default sensitivity level 1 mapping level 2 mapping function level 2 interrupt handler fiq level irq_0 ? fiq interrupt from level 2 handler camera_if_interrupt level irq_1 ? camera interface interrupt reserved ? irq_2 ? reserved, keep masked external fiq edge irq_3 ? external fiq interrupt mcbsp2 tx int edge irq_4 ? mcbsp2 transmit interrupt mcbsp2 rx int edge irq_5 ? mcbsp2 receive interrupt irq_rtdx level irq_6 ? real-time data exchange interrupt (for rtdx emulation tools) irq_dsp_mmu_abort level irq_7 ? dsp mmu abort interrupt irq_host_int level irq_8 ? irq_abort level irq_9 ? irq_dsp_mailbox1 level irq_10 ? dsp2arm1 mailbox interrupt irq_dsp_mailbox2 level irq_11 ? dsp2arm2 mailbox interrupt reserved ? irq_12 ? reserved, keep masked irq_tipb_bridge_private level irq_13 ? tipb private bridge interrupt irq_gpio level irq_14 ? mpu interrupt for mpu-owned shared gpi irq_uart3 level irq_15 ? uart3 interrupt irq_timer3 edge irq_16 ? mpu timer 3 interrupt irq_lb_mmu level irq_17 ? local bus mmu interrupt reserved ? irq_18 ? reserved, keep masked irq_dma_ch0_ch6 level irq_19 ? system dma channel 0 and 6 interrupt irq_dma_ch1_ch7 level irq_20 ? system dma channel 1 and 7 interrupt irq_dma_ch2_ch8 level irq_21 ? system dma channel 2 and 8 interrupt irq_dma_ch3 level irq_22 ? system dma channel 3 interrupt irq_dma_ch4 level irq_23 ? system dma channel 4 interrupt irq_dma_ch5 level irq_24 ? system dma channel 5 interrupt irq_dma_ch_lcd level irq_25 ? system dma lcd channel interrupt irq_timer1 edge irq_26 ? mpu timer 1 interrupt irq_wd_timer edge irq_27 ? mpu watchdog timer interrupt irq_tipb_bridge_public level irq_28 ? tipb public bridge interrupt irq_local_bus_if level irq_29 ? local bus interrupt irq_timer2 edge irq_30 ? mpu timer 2 interrupt irq_lcd_ctrl level irq_31 ? lcd controller interrupt fac level irq_0 irq_0 frame adjustment counter interrupt kbd edge irq_0 irq_1 keyboard interrupt microwire_tx edge irq_0 irq_2 microwire transmit interrupt microwire_rx edge irq_0 irq_3 microwire receive interrupt i2c edge irq_0 irq_4 i 2 c interrupt mpuio level irq_0 irq_5 mpuio interrupt functional overview 100 august 2002 ? revised august 2003 sprs197b table 3?73. mpu level 1 and level 2 interrupt mappings (continued) interrupt function level 2 mapping level 1 mapping default sensitivity usb_hhc1 level irq_0 irq_6 usb host hhc1 interrupt reserved ? irq_0 irq_7 reserved ? irq_0 irq_8 reserved ? irq_0 irq_9 mcbsp3_tx_int edge irq_0 irq_10 mcbsp3 transmit interrupt mcbsp3_rx_int edge irq_0 irq_11 mcbsp3 receive interrupt mcbsp1_tx_int edge irq_0 irq_12 mcbsp1 transmit interrupt mcbsp1_rx_int edge irq_0 irq_13 mcbsp1 receive interrupt uart1 level irq_0 irq_14 uart1 interrupt uart2 level irq_0 irq_15 uart2 interrupt mcsi1_tx_rx_fe_int level irq_0 irq_16 mcsi1 combined transmit/receive/frame error interrupt mcsi2_tx_rx_fe_int level irq_0 irq_17 mcsi2 combined transmit/receive/frame error interrupt reserved ? irq_0 irq_18 reserved, keep masked reserved ? irq_0 irq_19 reserved, keep masked usb_clnt_geni_int level irq_0 irq_20 usb function general-purpose interrupt 1wire_int level irq_0 irq_21 1-wire interface interrupt timer_32k_int edge irq_0 irq_22 32k timer interrupt mmc_int level irq_0 irq_23 mmc/sd interrupt ulpd_int level irq_0 irq_24 ultra-low power device module interrupt rtc_periodic_timer edge irq_0 irq_25 real-time clock periodic timer interrupt rtc_alarm level irq_0 irq_26 real-time clock alarm interrupt reserved ? irq_0 irq_27 dspmmu_irq level irq_0 irq_28 dsp mmu interrupt usb_func_irq_iso_on level irq_0 irq_29 usb function isochronous on interrupt usb_func_irq_noniso_on level irq_0 irq_30 usb function non-isochronous on interrupt mcbsp2_rx_overflow_int edge irq_0 irq_31 mcbsp2 receive overflow interrupt functional overview 101 august 2002 ? revised august 2003 sprs197b table 3?74. dsp level 1 interrupt mappings interrupt dsp interrupt dsp ifr/imr register bit vector location (byte address) priority function reset ? ? fff00h 0 dsp reset interrupt nmi ? ? fff08h 1 dsp nonmaskable interrupt emulator_test int2 2 fff10h 3 dsp emulator/test interrupt level2_inth_fiq int3 3 fff18h 5 fiq interrupt from dsp level 2 handler tc_abort int4 4 fff20h 6 traffic controller abort interrupt mailbox_1 (arm2dsp1) int5 5 fff28h 7 mpu-to-dsp mailbox 1 interrupt reserved int6 6 fff30h 9 unused, keep masked gpio int7 7 fff38h 10 interrupt for dsp-owned shared gpio timer3 int8 8 fff40h 11 dsp timer 3 interrupt dma_channel_1 int9 9 fff48h 13 dsp dma channel 1 interrupt mpu int10 10 fff50h 14 mpu interrupt to dsp reserved int11 11 fff58h 15 unused, keep masked uart3 int12 12 fff60h 17 uart interrupt wdgtimer int13 13 fff68h 18 dsp watchdog timer interrupt dma_channel_4 int14 14 fff70h 21 dsp dma channel 4 interrupt dma_channel_5 int15 15 fff78h 22 dsp dma channel 5 interrupt emif int16 16 fff80h 4 interrupt for dma emif interface to traffic controller local_bus int17 17 fff88h 8 local bus interrupt dma_channel_0 int18 18 fff90h 12 dsp dma channel 0 interrupt mailbox2 (arm2dsp2) int19 19 fff98h 16 mpu-to-dsp mailbox 2 interrupt dma_channel_2 int20 20 fffa0h 19 dsp dma channel 2 interrupt dma_channel_3 int21 21 fffa8h 20 dsp dma channel 3 interrupt timer2 int22 22 fffb0h 23 dsp timer 2 interrupt timer1 int23 23 fffb8h 24 dsp timer 1 interrupt functional overview 102 august 2002 ? revised august 2003 sprs197b table 3?75. dsp level 2 interrupt mappings interrupt default sensitivity level 1 mapping level 2 mapping function mcbsp3_tx edge int3 irq_0 mcbsp3 transmit interrupt mcbsp3_rx edge int3 irq_1 mcbsp3 receive interrupt mcbsp1_tx edge int3 irq_2 mcbsp1 transmit interrupt mcbsp1_rx edge int3 irq_3 mcbsp1 receive interrupt uart2 level int3 irq_4 uart2 interrupt uart1 level int3 irq_5 uart1 interrupt mcsi1_tx level int3 irq_6 mcsi1 transmit interrupt mcsi1_rx level int3 irq_7 mcsi1 receive interrupt mcsi2_tx level int3 irq_8 mcsi2 transmit interrupt mcsi2_rx level int3 irq_9 mcsi2 receive interrupt mcsi1_frame_error_int level int3 irq_10 mcsi1 frame error interrupt mcsi2_frame_error_int level int3 irq_11 mcsi2 frame error interrupt reserved ? int3 irq_12 reserved, keep masked reserved ? int3 irq_13 reserved, keep masked reserved ? int3 irq_14 reserved, keep masked reserved ? int3 irq_15 reserved, keep masked documentation support 103 august 2002 ? revised august 2003 sprs197b 4 documentation support extensive documentation supports all omap platform of devices from product announcement through applications development. the following types of documentation are available to support the design and use of the omap platform of dual-core processor devices: ? device-specific data sheets ? development-support tools ? hardware and software application reports a series of dsp textbooks is published by prentice-hall and john wiley & sons to support digital signal processing research and education. the tms320 dsp newsletter, details on signal processing , is published quarterly and distributed to update tms320 dsp customers on product information. information regarding texas instruments (ti) omap and dsp products is also available on the worldwide web at http://www.ti.com uniform resource locator (url). 4.1 device and development-support tool nomenclature to designate the stages in the product development cycle, ti assigns prefixes to the part numbers of all tms320 ? dsp devices and support tools. each tms320 ? dsp commercial family member has one of three prefixes: tmx, tmp, or tms. texas instruments recommends two of three possible prefix designators for support tools: tmdx and tmds. these prefixes represent evolutionary stages of product development from engineering prototypes (tmx / tmdx) through fully qualified production devices/tools (tms / tmds). device development evolutionary flow: tmx experimental device that is not necessarily representative of the final device? s electrical specifications tmp final silicon die that conforms to the device?s electrical specifications but has not completed quality and reliability verification tms fully qualified production device support tool development evolutionary flow: tmdx development-support product that has not yet completed texas instruments internal qualification testing. tmds fully qualified development-support product tmx and tmp devices and tmdx development-support tools are shipped with appropriate disclaimers describing their limitations and intended uses. experimental devices (tmx) may not be representative of a final product and t exas instruments reserves the right to change or discontinue these products without notice. tms devices and tmds development-support tools have been characterized fully, and the quality and reliability of the device have been demonstrated fully. ti?s standard warranty applies. predictions show that prototype devices ( tmx or tmp) have a greater failure rate than the standard production devices. texas instruments recommends that these devices not be used in any production system because their expected end-use failure rate still is undefined. only qualified production devices are to be used. tms320 is a trademark of texas instruments. electrical specifications 104 august 2002 ? revised august 2003 sprs197b 5 electrical specifications this section provides the absolute maximum ratings and the recommended operating conditions for the omap5910 device. all electrical and switching characteristics in this data manual are valid over the recommended operating conditions unless otherwise specified. 5.1 absolute maximum ratings the list of absolute maximum ratings are specified over operating case temperature. stresses beyond those listed under ?absolute maximum ratings? may cause permanent damage to the device. these are stress ratings only, and functional operation of the device at these or any other conditions beyond those indicated under section 5.2, recommended operating conditions, is not implied. exposure to absolute-maximum-rated conditions for extended periods may affect device reliability. all supply voltage values (core and i/o) are with respect v ss . note: the omap5910 device has undergone charged device model electrostatic discharge (esd) testing, passing at the 500 v level. human body model (hbm) esd testing per eia/jesd22-a114 has also been performed. test results indicate that the omap5910 passes at a 500 v hbm (maximum) level. caution in handling devices is advised. this section provides the absolute maximum ratings for the omap5910 device. supply voltage range (core), cv dd ,cv dd1/2/3/4/a ?0.3 v to 1.8 v . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . supply voltage range (i/o), dv dd1/2/3/4/5 ?0.3 v to 4 v . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . input voltage range, v i (12-mhz and 32-khz oscillator) ?0.3 v to cv dd + 0.5 v . . . . . . . . . . . . . . . . . . . . . . . input voltage range, v i (standard lvcmos) ?0.3 v to dv dd + 0.5 v . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . input voltage range, v i (fail-safe lvcmos) ?0.3 v to 4.5 v . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . input voltage range, v i (usb transceivers) ?0.3 v to dv dd + 0.5 v . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . input voltage range, v i (i 2 c) ?0.3 v to 4.5 v . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . output voltage range, v o (standard lvcmos) ?0.3 v to dv dd + 0.5 v . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . output voltage range, v o (fail-safe lvcmos) ?0.3 v to 4.5 v . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . output voltage range, v o (usb transceivers) ?0.3 v to dv dd + 0.5 v . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . output voltage range, v o (i 2 c) ?0.3 v to 4.5 v . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . operating temperature range, t c ?40 c to 85 c . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . storage temperature range, t stg ?55 c to 150 c . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . electrical specifications 105 august 2002 ? revised august 2003 sprs197b 5.2 recommended operating conditions min nom max unit cv dd device supply voltage, core ? low power standby mode ? 1 1.1 1.675 v cv dd cv dd1/2/3/4/a device supply voltage, core ? active mode 1.525 1.6 1.675 v dv dd1 device supply voltage, i/o (peripheral i/o) 2.5 2.75 or 3.3 3.6 v dv dd2 device supply voltage, i/o (usb transceiver) 3 3.3 3.6 v dv dd3 device supply voltage, i/o low-voltage range 1.65 1.8 1.95 v dv dd3 device supply voltage, i/o (mcsi2, mcbsp2, gpio[9:8]) high-voltage range 2.5 2.75 or 3.3 3.6 v dv dd4 device supply voltage, i/o low-voltage range 1.65 1.8 1.95 v dv dd4 device supply voltage, i/o (sdram interface) high-voltage range 2.5 2.75 or 3.3 3.6 v dv dd5 device supply voltage, i/o low-voltage range 1.65 1.8 2 v dv dd5 device supply voltage, i/o (flash interface) high-voltage range 2.5 2.75 or 3.3 3.6 v cv dd ? dv dd device supply voltage difference ? 1.65 v dv dd ? cv dd device supply voltage difference ? 2.6 v v ss supply voltage, gnd 0 v standard lvcmos 0.7 dv dd dv dd v ih high-level input voltage, i/o fail-safe lvcmos 0.7 dv dd dv dd v v ih high-level input voltage, i/o usb.dp, dm (mode 1) 2 dv dd v i 2 c 0.7 dv dd dv dd standard lvcmos 0 0.3 dv dd v il low-level input voltage, i/o fail-safe lvcmos 0 0.3 dv dd v v il low-level input voltage, i/o usb.dp, dm (mode 1) 0 0.8 v i 2 c 0 0.3 dv dd v i input voltage usb.dp, dm (mode 2) 0.8 2.5 v v i input voltage osc1 and osc32k pins cv dd v v id differential input voltage, i/o usb.dp, dm (mode 2) 200 mv 2-ma drive strength buffers ?2 4-ma drive strength buffers ?4 i oh high-level output current 8-ma drive strength buffers ?8 ma i oh high-level output current 18.3-ma drive strength buffers ?18.3 ma 2-ma drive strength buffers 2 4-ma drive strength buffers 4 i ol low-level output current 6-ma drive strength buffers 6 ma i ol low-level output current 8-ma drive strength buffers 8 ma 18.3-ma drive strength buffers 18.3 t c operating case temperature ?40 85 c ? all core voltage supplies should be tied to the same voltage level (within 0.3 v). ? low power standby is defined as follows: the device is in deep sleep mode and low_pwr = 1. the device runs from 32 khz clock i n this mode. high and low voltage ranges are selectable via software configuration. ? in systems where the cv ddx and dv ddx power supplies are ramped at generally the same time (within 500 ms of one another), there are no specific power sequencing requirements for the supplies. the only sequencing requirement is that the maximum voltage differenc e between cv dd and dv dd is not exceeded for greater than 500 ms. likewise, if different voltages are used for the separate dv ddx supplies, all dv ddx supplies should be ramp up to valid voltage levels within 500ms of one another. electrical specifications 106 august 2002 ? revised august 2003 sprs197b 5.3 electrical characteristics over recommended operating case temperature range (unless otherwise noted) parameter test conditions min typ max unit high-level output standard lvcmos dv dd = 3.3 v, i oh = max 0.8 dv dd v oh high-level output voltage fail-safe lvcmos dv dd = 3.3 v, i oh = max 0.8 dv dd v v oh voltage usb.dp, dm i o = ?12 ma dv dd ? 0.5 v standard lvcmos dv dd = 3.3 v, i ol = max 0.22 dv dd fail-safe lvcmos dv dd = 3.3 v, i ol = max 0.22 dv dd low-level output usb.dp, dm i o = 12 ma 0.5 v ol low-level output voltage fast mode at 6-ma load 0.6 v v ol voltage i 2 c fast mode at 3-ma load 0.4 v i 2 c standard mode at 3-ma load 0.4 fail-safe lvcmos inputs without internal pullups/pulldowns enabled v i = v i max to v i min ? 20 20 other inputs without internal pullups/pulldowns enabled v i = v i max to v i min ?1 1 i i input current input pins with 20- a pulldowns enabled dv dd = max, v i = v ss to v dd 6 20 60 a i i input current input pins with 100- a pulldowns enabled dv dd = max, v i = v ss to v dd 30 100 300 a input pins with 20- a pullups enabled cv dd = max, v i = v ss to v dd ? 60 ? 20 ? 6 input pins with 100- a pullups enabled dv dd = max, v i = v ss to v dd ? 20 ? 100 ? 30 i oz input current for outputs in high-impedance ? 20 20 a i ddc (q) core voltage supply current, quiescent sum of cv ddx currents. (deep sleep mode with cv dd = 1.6v) 115 a i ddc (q ) core voltage supply current, quiescent sum of cv ddx currents. (deep sleep mode with cv dd = 1.1v) 50 a i ddc (a) core voltage supply current, active sum of cv ddx currents (case 1 ? ). 150 ma i ddc (a ) core voltage supply current, active sum of cv ddx currents (case 2 ? ). 170 ma i ddcp (a) core and i/o voltage supply current, active sum of cv ddx and dv ddx currents (case 3 ). 45 ma i ddcp (a ) core and i/o voltage supply current, active sum of cv ddx and dv ddx currents (case 4 ? ). 6 ma c i input capacitance usb.dp,dm 7 pf c i input capacitance all other i/o pins 4 pf c o output capacitance usb.dp,dm 7 pf c o output capacitance all other i/o pins 4 pf ? case 1: mpu running os, dsp running gsm vocoder from internal memory, dsp mmu and all clock domains active, no lcd activity. ? case 2: same conditions as case 1 only dsp running from external memory with i-cache enabled. case 3: only lcd activity (mpu and dsp idled with clocks off). lcd running 320x240 tft at 70 frames per second with frame buffer in in ternal memory (dpll at 120mhz). ? case 4: same as case 3 only lcd running at 10 frames per second with dpll at 6mhz. electrical specifications 107 august 2002 ? revised august 2003 sprs197b tester pin electronics v load i ol-test c t i oh-test output under test 50 ? where: i ol-test = 5 ma (all outputs) i oh-test = 300 a (all outputs) v load = 5 v c t = 10 pf maximum and 5 pf minimum for emiff (50 pf maximum and 5 pf minimum for emifs and all other i/o pads). figure 5?1. 3.3-v test load circuit 5.4 package thermal resistance characteristics table 5?1 provides the thermal resistance characteristics for the recommended package types used on the omap5910 device. table 5?1. thermal resistance characteristics r ja ( c/w) r jc ( c/w) board type ? 34.01 7.43 high-k 63.26 7.13 low-k ? board types are as defined by jedec. reference jedec standard jesd51?9, test boards for area array surface mount package thermal measurements. 5.5 timing parameter symbology timing parameter symbols used in the timing requirements and switching characteristics tables are created in accordance with jedec standard 100. to shorten the symbols, some of the pin names and other related terminology have been abbreviated as follows: lowercase subscripts and their meanings: letters and symbols and their meanings: a access time h high c cycle time (period) l low d delay time v valid dis disable time z high impedance en enable time f fall time h hold time r rise time su setup time t transition time v valid time w pulse duration (width) x unknown, changing, or don?t care level electrical specifications 108 august 2002 ? revised august 2003 sprs197b 5.6 clock specifications this section provides the timing requirements and switching characteristics for the omap5910 system clock signals. 5.6.1 32-khz oscillator and input clock the 32.768-khz clock signal (often abbreviated to 32-khz) may be supplied by either the on-chip 32-khz oscillator (requiring an external crystal) or an external cmos signal. the state of the clk32k_ctrl pin determines which is used. the on-chip oscillator requires an external 32.768-khz crystal connected across the osc32k_in and osc32k_out pins. the connection of the required circuit, consisting of the crystal and two load capacitors, is shown in figure 5?2. the load capacitors, c 1 and c 2 , should be chosen such that the equation below is satisfied (recommended values are c 1 = c 2 = 10 pf). c l in the equation is the load specified for the crystal. all discrete components used to implement the oscillator circuit should be placed as close as possible to the associated oscillator pins (osc32k_in and osc32k_out) and to the v ss pin closest to the oscillator pins (gzg ball v12 or gdy ball f6). note: the 32.768-khz oscillator is powered by the cv dd supply. if an external clock source is used instead of using the on-chip oscillator, care must be taken that the voltage level driven onto the osc32k_in and osc32k_out pins is no greater than the cv dd voltage level. c l c 1 c 2 ( c 1 c 2 ) osc32k_in osc32k_out c1 c2 crystal v ss 32.768 khz figure 5?2. 32-khz oscillator external crystal table 5?2 shows the switching characteristics of the 32-khz oscillator and table 5?3 shows the input requirements of the 32-khz clock input. table 5?2. 32-khz oscillator switching characteristics parameter min typ max unit start-up time (from power up until oscillating at stable frequency of 32.768 khz) 200 800 ms i dda , active current consumption 4 a oscillation frequency 32.768 khz electrical specifications 109 august 2002 ? revised august 2003 sprs197b table 5?3. 32-khz input clock timing requirements no. min nom max unit ck1 t cyc frequency 32.768 khz ck2 t f fall time 25 ns ck3 t r rise time 25 ns ck4 duty cycle (high-to-low ratio) 30% 70% % ck5 frequency stability ?70 70 ppm ck1 ck2 ck3 clk32k_in figure 5?3. 32-khz input clock 5.6.2 base oscillator (12 mhz or 13 mhz) and input clock the internal base system oscillator is enabled following a device reset. the oscillator requires an external crystal to be connected across the osc1_in and osc1_out pins. if the internal oscillator is not used (configured in software), an external clock source must be applied to the osc1_in pin and the osc1_out pin must be left unconnected. because the internal oscillator can be used as a clock source to the omap dpll, the 12- or 13-mhz crystal oscillation frequency can be multiplied to generate the dsp clock, mpu clock, traffic controller clock. the crystal must be in fundamental-mode operation, and parallel resonant, with a maximum effective series resistance of 60 ? maximum. the connection of the required circuit, consisting of the crystal and two load capacitors, is shown in figure 5?4. the load capacitors, c 1 and c 2 , must be chosen such that the equation below is satisfied (recommended values are c 1 = c 2 = 10 pf). c l in the equation is the load specified for the crystal. all discrete components used to implement the oscillator circuit must be placed as close as possible to the associated oscillator pins (osc1_in and osc1_out) and to the v ss pins closest to the oscillator pins (gzg balls aa1/y3 or gdy balls e13/k9). note: the base oscillator is powered by the cv dd supply. if an external clock source is used instead of using the on-chip oscillator, care must be taken that the voltage level driven onto the osc1_in pin is no greater than the cv dd voltage level. c l c 1 c 2 ( c 1 c 2 ) osc1_in osc1_out c1 c2 12 or 13 mhz crystal figure 5?4. internal system oscillator external crystal electrical specifications 110 august 2002 ? revised august 2003 sprs197b if usb host function is used, it is recommended that a very low ppm crystal ( 50 ppm) be used for the 12- or 13-mhz oscillator circuit. if the usb host function is not used, then a crystal of 180 ppm is recommended. when selecting a crystal, the system design must take into account the temperature and aging characteristics of a crystal versus the user environment and expected lifetime of the system. table 5?4 shows the switching characteristics of the base oscillator. table 5?4. base oscillator switching characteristics parameter min typ max unit start-up time (from power up until oscillating at stable frequency of 12 or 13 mhz) 1 4 ms i dda , active current consumption 350 a oscillation frequency 12 or 13 mhz 5.6.3 internal clock speed limitations table 5?5 provides a summary of the maximum frequencies that each clock domain may be configured to run on the omap5910 device table 5?5. internal clock speed limitations clock max operating frequency unit mpu (clkm1) 150 mhz dsp (clkm2) 150 mhz tc (clkm3) 75 mhz dpll1 150 mhz all clock domains must be derived from the same dpll1 frequency setting; therefore, the following conditions must be satisfied where ?m?, ?n?, and ?o? are each equal to either 1, 2, 4, or 8: ? mpu frequency = (dpll1 clock frequency) / m ? dsp frequency = (dpll1 clock frequency) / n ? tc frequency = (dpll1 clock frequency) / o for example, the following configuration is valid: ? mpu/dsp/tc = 150 mhz/150 mhz/75 mhz, where m = n = 1 and o = 2 electrical specifications 111 august 2002 ? revised august 2003 sprs197b 5.7 reset timings this section provides the timing requirements for the omap5910 hardware reset signals. 5.7.1 omap5910 device reset the pwron_reset signal is the active-low asynchronous reset input responsible for the reset of the entire omap5910 device. when using an external crystal to supply the 32-khz system clock, pwron_reset must be asserted low a minimum of two 32-khz clock cycles longer than the worst-case start-up time of the 32-khz oscillator after stable power supplies (see figure 5?5). if an external cmos input signal is used to source 32 khz, pwron_reset must be asserted low a minimum of two 32-khz clock cycles after stable power supplies. see table 5?6 and table 5?7. table 5?6. omap5910 device reset timing requirements no. min max unit rs1 t w(pwron_rst) pulse duration, pwron_reset low 800 ms table 5?7. omap5910 device reset switching characteristics ? no. parameter min max unit rs2 t d(pwronh-rsth) delay time, pwron_reset high to rst_out high t + 10 s ? p = period of 32-khz clock, c = value of ulpd wakeup time setup register, setup_ulpd1_reg (default 03ffh), t = p*c cv ddx dv ddx osc32k_in pwron_reset rs1 rst_out rs2 worst-case oscillator start-up time 2 cycles figure 5?5. device reset timings electrical specifications 112 august 2002 ? revised august 2003 sprs197b 5.7.2 omap5910 mpu core reset the mpu_rst signal is the active-low asynchronous input responsible for the reset of the omap5910 mpu core. stable power supplies are assumed prior to mpu_rst assertion. figure 5?6 illustrates the behavior of mpu_rst and rst_out . in figure 5.6, a logic high level is assumed on the pwron_reset input. in the case where an application ties the pwron_reset and mpu_rst together, the behavior described in section 5.7.1, omap5910 device reset , will override. see table 5?8 and table 5?9. table 5?8. mpu_rst timing requirements no. min max unit m3 t w(mpu_rst) pulse duration, mpu_rst low 50 s table 5?9. mpu_rst switching characteristics ? no. parameter min max unit m1 t d(mpul?rstl) delay time, mpu_rst low to rst_out low 1 s m2 t d(mpuh?rsth) delay time, mpu_rst high to rst_out high mpu_rst asserted during omap5910 awake state 10 s m2 t d(mpuh?rsth ) delay time, mpu_rst high to rst_out high mpu_rst asserted during omap5910 deep sleep state t + 10 s ? p = period of 32-khz clock, c = value of ulpd wakeup time setup register, setup_ulpd1_reg (default 03ffh), t = p*c mpu_rst rst_out m1 m2 m3 figure 5?6. mpu core reset timings electrical specifications 113 august 2002 ? revised august 2003 sprs197b 5.8 external memory interface timing 5.8.1 emifs/flash interface timing table 5?10 and t able 5?11 assume testing over recommended operating conditions (see figure 5?7 through figure 5?11). table 5?10. emifs/flash interface timing requirements no. dv dd5 = 1.8 v nominal dv dd5 = 2.75 v nominal dv dd5 = 3.3 v nominal unit no. min max min max min max unit f6 t su(dv?clkh) setup time, read data valid async modes (rt = 0) ? 18 18 15 ns f6 t su(dv?clkh ) setup time, read data valid before flash.clk high sync modes (rt = 1) ? 2 2 2 ns f7 t h(clkh?rdv) hold time, read data valid async modes (rt = 0) ? 29 29 26 ns f7 t h(clkh?rdv ) hold time, read data valid after flash.clk high sync modes (rt = 1) ? 2 2 2 ns ? when the rt field in the emifs configuration register is set, input data is retimed to the external flash.clk signal. rt=1 sett ing is only valid in synchronous modes (protocols 1 and 2). for async modes, t d(clkh?csv ) with respect to internal flash.clk is given as 0 to allow for other signals reference to flash.csx . the external flash.clk is disabled for async modes. electrical specifications 114 august 2002 ? revised august 2003 sprs197b table 5?11. emifs/flash interface switching characteristics no. parameter dv dd5 = 1.8 v nominal dv dd5 = 2.75 v nominal dv dd5 = 3.3 v nominal unit no. parameter min max min max min max unit f1 t d(clkh?csv) delay time, flash.clk high async modes ? 0 0 0 ns f1 t d(clkh?csv ) flash.clk high to flash.csx transition sync modes ?1 12 ?1 11 ?1 10 ns f2 t d(clkh?bev) delay time, flash.clk high async modes ? ?9 2 ?9 2 ?9 2 ns f2 t d(clkh?bev ) flash.clk high to flash.bex valid sync modes ?1 4 ?1 4 ?1 3 ns f3 t d(clkh?beiv) delay time, flash.clk high async modes ? ?9 2 ?9 2 ?9 2 ns f3 t d(clkh?beiv ) flash.clk high to flash.bex invalid sync modes ?1 4 ?1 4 ?1 3 ns f4 t d(clkh?av) delay time, flash.clk high async modes ? ?7 6 ?7 6 ?7 6 ns f4 t d(clkh?av) flash.clk high to address valid sync modes ?1 9 0 8 0 7 ns f5 t d(clkh?aiv) delay time, flash.clk high async modes ? ?7 6 ?7 6 ?7 6 ns f5 t d(clkh?aiv ) flash.clk high to address invalid sync modes ?1 9 ?1 8 ?1 7 ns f8 t d(clkh?adv) delay time, flash.clk high async modes ? ?10 1 ?10 1 ?9 1 ns f8 t d(clkh?adv ) flash.clk high to flash.adv transition sync modes ?1 3 ?1 3 ?1 2 ns f9 t d(clkh?oev) delay time, flash.clk high async modes ? ?8 1 ?8 1 ?8 1 ns f9 t d(clkh?oev ) flash.clk high to flash.oe transition sync modes ?1 4 ?1 3 ?1 3 ns f12 t d(clkh?wev) delay time, flash.clk high async modes ? ?8 1 ?8 1 ?8 1 ns f12 t d(clkh?wev ) flash.clk high to flash.we transition sync modes ?1 4 ?1 3 ?1 3 ns f13 t d(clkh?wdv) delay time, flash.clk high async modes ? ?15 7 ?15 7 ?14 7 ns f13 t d(clkh?wdv ) flash.clk high to write data valid sync modes ?4 7 ?3 6 ?3 6 ns f14 t d(clkh?wdiv) delay time, flash.clk high async modes ? ?15 7 ?15 7 ?15 7 ns f14 t d(clkh?wdiv ) flash.clk high to write data invalid sync modes ?4 7 ?3 6 ?3 6 ns f15 t d(clkh?dhz) delay time, flash.clk high to data bus high-impedance ? 16 15 14 ns f16 t d(clkh?dlz) delay time, flash.clk high to data bus driven ?4 7 ?3 6 ?3 6 ns f17 t d(clkh?baav) ? delay time, flash.clk high to flash.baa transition ? ?1 + 0.5p 8 + 0.5p ?1 + 0.5p 7.5 + 0.5p ?1 + 0.5p 7.5 + 0.5p ns ? data is referenced to the internal flash.clk. for async modes, t d(clkh?csv ) with respect to internal flash.clk is given as 0 to allow for other signals reference to flash.csx . the external flash.clk is disabled for async modes. ? p = period of undivided traffic controller clock regardless of flash.clk divider configuration electrical specifications 115 august 2002 ? revised august 2003 sprs197b f1 f2 f4 f8 f9 f9 f8 f7 f6 f5 f3 f1 d1 valid a1 flash.clk ? flash.csx flash.be[1:0] flash.a[24:1] flash.d[15:0] flash.adv flash.oe flash.we (internal) n cycles ? ? flash.clk is not driven during this mode of operation. the signal shown represents the internal flash.clk signal given as a ref erence to express relative timings. ? number of cycles is configurable via emifs setup registers. figure 5?7. asynchronous memory read timing electrical specifications 116 august 2002 ? revised august 2003 sprs197b f1 f2 f4 f8 f9 f9 f8 f7 f6 f5 f3 f1 d1 upper valid a1 flash.clk ? flash.csx flash.be[1:0] flash.a[24:1] flash.d[15:0] flash.adv flash.oe flash.we f6 f7 d1 lower (internal) m cycles ? n cycles ? ? flash.clk is not driven during this mode of operation. the signal shown represents the internal flash.clk signal given as a ref erence to express relative timings. ? number of cycles is configurable via emifs setup registers. figure 5?8. asynchronous 32-bit read electrical specifications 117 august 2002 ? revised august 2003 sprs197b f1 f2 f4 f8 f9 f9 f8 f7 f6 f5 f3 f1 d4 valid a1 flash.clk ? flash.csx flash.be[1:0] flash.a[24:3] flash.d[15:0] flash.adv flash.oe flash.we f6 f7 d1 flash.a[2:1] d2 d3 word 0 word 1 word 2 word 3 f5 f5 f4 f4 (internal) m cycles ? p cycles ? p cycles ? p cycles ? ? flash.clk is not driven during this mode of operation. the signal shown represents the internal flash.clk signal given as a ref erence to express relative timings. ? number of cycles is configurable via emifs setup registers. figure 5?9. asynchronous read ? page mode rom electrical specifications 118 august 2002 ? revised august 2003 sprs197b f1 f2 f4 f5 f3 f1 valid a1 flash.clk ? flash.csx flash.be[1:0] flash.a[24:1] flash.d[15:0] flash.adv flash.oe flash.we f15 f14 f16 f13 f8 f8 f12 f12 d1 (internal) p cycles ? n cycles ? m cycles ? q cycles ? adv width we width cs hold wait-states ? flash.clk is not driven during this mode of operation. the signal shown represents the internal flash.clk signal given as a ref erence to express relative timings. ? number of cycles is configurable via emifs setup registers. figure 5?10. asynchronous memory write timing electrical specifications 119 august 2002 ? revised august 2003 sprs197b valid a1 flash.clk ? flash.csx flash.be[1:0] flash.a[24:1] flash.d[15:0] flash.adv flash.baa f1 f2 f1 f3 f4 f5 d1 d2 d3 d4 f6 f7 f6 f7 f8 f8 f17 f17 f9 f9 flash.oe flash.we n cycles ? m cycles ? adv width wait-states q cycles ? clk start (external) ? flash.clk is only driven during the active portion of the cycle. for reference, the dashed line shows flash.clk as if it were c ontinuous. ? number of cycles is configurable via emifs setup registers. figure 5?11. synchronous burst read electrical specifications 120 august 2002 ? revised august 2003 sprs197b 5.8.2 emiff/sdram interface timing table 5?12 and table 5?13 assume testing over recommended operating conditions (see figure 5?12 through figure 5?17). table 5?12. emiff/sdram interface timing requirements ? no. dv dd4 = 1.8 v nominal dv dd4 = 2.75 v nominal dv dd4 = 3.3 v nominal unit no. min max min max min max unit sd7 t su(dv-clkh) setup time, read data valid before sdram.clk high 2 2 2 ns sd8 t h(clkh-dv) hold time, read data valid after sdram.clk high 1 1 1 ns ? timing requirements are with the sd_ret field equal to 1 in the emiff configuration register. table 5?13. emiff/sdram interface switching characteristics no. parameter dv dd4 = 1.8 v nominal dv dd4 = 2.75 v nominal dv dd4 = 3.3 v nominal unit no. parameter min max min max min max unit sd1 t c(clk) cycle time, sdram.clk h ? h ? h ? ns sd2 t w(clk) pulse duration, sdram.clk high/low 2.5 2.5 2.5 ns sd3 t d(clkh-dqmv) delay time, sdram.clk high to sdram.dqmx valid 1.5 9 1.5 9 1.5 9 ns sd4 t d(clkh-dqmiv) delay time, sdram.clk high to sdram.dqmx invalid 1.5 9 1.5 9 1.5 9 ns sd5 t d(clkh-av) delay time, sdram.clk high to sdram.a[12:0] address valid 1.5 9 1.5 9 1.5 9 ns sd6 t d(clkh-aiv) delay time, sdram.clk high to sdram.a[12:0] address invalid 1.5 9 1.5 9 1.5 9 ns sd9 t d(clkh-sdcasl) delay time, sdram.clk high to sdram.cas low 1.5 9 1.5 9 1.5 9 ns sd10 t d(clkh-sdcash) delay time, sdram.clk high to sdram.cas high 1.5 9 1.5 9 1.5 9 ns sd11 t d(clkh-dv) delay time, sdram.clk high to sdram.d[15:0] data valid 1.5 9 1.5 9 1.5 9 ns sd12 t d(clkh-div) delay time, sdram.clk high to sdram.d[15:0] data invalid 1.5 9 1.5 9 1.5 9 ns sd13 t d(clkh-sdwel) delay time, sdram.clk high to sdram.we low 1.5 9 1.5 9 1.5 9 ns sd14 t d(clkh-sdweh) delay time, sdram.clk high to sdram.we high 1.5 9 1.5 9 1.5 9 ns sd15 t d(clkh-bav) delay time, sdram.clk high to sdram.ba[1:0] valid 1.5 9 1.5 9 1.5 9 ns sd16 t d(clkh-baiv) delay time, sdram.clk high to sdram.ba[1:0] invalid 1.5 9 1.5 9 1.5 9 ns sd17 t d(clkh-rasl) delay time, sdram.clk high to sdram.ras low 1.5 9 1.5 9 1.5 9 ns sd18 t d(clkh-rash) delay time, sdram.clk high to sdram.ras high 1.5 9 1.5 9 1.5 9 ns ? h = 1/2 cpu cycle. electrical specifications 121 august 2002 ? revised august 2003 sprs197b sdram.clk sdram.dqmx sdram.a[12:0] sdram.d[15:0] sdram.ras sdram.cas sdram.we ca1 ca2 d1 d2 sd10 sd6 sd8 sd7 read sd3 sd9 sd5 sdram.cke sdram.ba[1:0] bank address sd15 sd16 sd1 sd2 sd2 read burst terminate figure 5?12. 32-bit (2 x 16-bit) sdram rd (read) command (active row) sdram.clk sdram.dqmx sdram.a[12:0] sdram.d[15:0] sdram.ras sdram.cas sdram.we be1 be2 ca1 ca2 d1 d2 sd14 sd10 sd12 sd16 sd4 write write sd3 sd15 sd11 sd9 sd13 sdram.cke sdram.ba[1:0] bank address sd16 sd15 burst terminate figure 5?13. 32-bit (2 x 16-bit) sdram wrt (write) command (active row) electrical specifications 122 august 2002 ? revised august 2003 sprs197b sdram.clk sdram.dqmx sdram.a[12:0] sdram.d[15:0] sdram.ras sdram.cas sdram.we row address sd18 actv sd5 sd17 sdram.cke sdram.ba[1:0] bank activate sd15 figure 5?14. sdram actv (activate row) command sdram.clk sdram.dqmx sdram.a[12:11, 9:0] sdram.d[15:0] sdram.a[10] sdram.ras sdram.cas sdram.we sd14 sd18 sd6 dcab sd5 sd17 sd13 sdram.cke sdram.ba[1:0] figure 5?15. sdram dcab (precharge/deactivate row) command electrical specifications 123 august 2002 ? revised august 2003 sprs197b sdram.clk sdram.dqmx sdram.d[15:0] sdram.a[10] sdram.ras sdram.cas sdram.we sd10 sd18 refr sd17 sd9 sd5 sd6 sdram.cke sdram.a[12:11, 9:0] sdram.bax figure 5?16. sdram refr (refresh) command sdram.clk sdram.dqmx sdram.d[15:0] sdram.a10 sdram.ras sdram.cas sdram.we mrs value sd14 sd10 sd6 mrs sdram.cke sdram.a[9:0] sdram.ba[1:0] sd5 sd5 sd6 sd17 sd18 sd9 sd13 figure 5?17. sdram mrs (mode register set) command electrical specifications 124 august 2002 ? revised august 2003 sprs197b 5.9 multichannel buffered serial port (mcbsp) timings 5.9.1 mcbsp transmit and receive timings table 5?14 and table 5?15 assume testing over recommended operating conditions (see figure 5?18 and figure 5?19). in t able 5?14 and table 5?15, ?ext? indicates that the device pin is configured as an input (slave) driven by an external device and ?int? indicates that the pin is configured as an output (master). table 5?14. mcbsp timing requirements ?? no. min max unit m11 t c(ckrx) cycle time, clkr/x clkr/x ext 2p ns m12 t w(ckrx) pulse duration, clkr/x high or clkr/x low clkr/x ext 0.45p ns mcbsp1 clkr/x ext 12 m13 t r rise time, clkr/x, mcbsp2.fsr/x mcbsp2 clkr/x ext, mcbsp2.fs r/x ext 12 ns mcbsp3 clkr/x ext 6 mcbsp1 clkr/x ext 12 m14 t f fall time, clkr/x, mcbsp2.fsr/x mcbsp2 clkr/x ext, mcbsp2.fs r/x ext 12 ns mcbsp3 clkr/x ext 6 mcbsp1 clkx int 25 mcbsp1 (fsx) clkx ext 31 m15 t su(frh-ckrl) setup time, external receiver frame sync (fsr/x) mcbsp2 clkr int 25 ns m15 t su(frh-ckrl ) setup time, external receiver frame sync (fsr/x) high before clkr/x low mcbsp2 (fsr) clkr ext 7 ns high before clkr/x low mcbsp3 clkx int 24 mcbsp3 (fsx) clkx ext 15 mcbsp1 clkx int 3 mcbsp1 (fsx) clkx ext 16 m16 t h(ckrl-frh) hold time, external receiver frame sync (fsr/x) high mcbsp2 clkr int 3 ns m16 t h(ckrl-frh) hold time, external receiver frame sync (fsr/x) high after clkr/x low mcbsp2 (fsr) clkr ext 3 ns after clkr/x low mcbsp3 clkx int 13 mcbsp3 (fsx) clkx ext 13 mcbsp1 clkx int 21 mcbsp1 clkx ext 3 m17 t su(drv-ckrl) setup time, dr valid before clkr/x low mcbsp2 clkr int 22 ns m17 t su(drv-ckrl ) setup time, dr valid before clkr/x low mcbsp2 clkr ext 3 ns mcbsp3 clkx int 19 mcbsp3 clkx ext 10 ? polarity bits clkrp = clkxp = fsrp = fsxp = 0. if the polarity of any of the signals is inverted, then the timing references of that signal are also inverted. ? p = 1/(base frequency) for mcbsp 1 and 3, or 1/(armper_ck clock frequency) in nanoseconds (ns) for mcbsp 2. base frequency is 12 or 13 mhz. for mcbsp1 and mcbsp2, the receiver clock and frame sync inputs are driven by fsx and clkx via internal loopback connections en abled via software configuration. electrical specifications 125 august 2002 ? revised august 2003 sprs197b table 5?14. mcbsp timing requirements ?? (continued) no. unit max min mcbsp1 clkx int 3 mcbsp1 clkx ext 3 m18 t h(ckrl-drv) hold time, dr valid after clkr/x low mcbsp2 clkr int 3 ns m18 t h(ckrl-drv) hold time, dr valid after clkr/x low mcbsp2 clkr ext 3 ns mcbsp3 clkx int 3 mcbsp3 clkx ext 3 mcbsp1 clkx int 30 mcbsp1 clkx ext 25 m19 t su(fxh-ckxl) setup time, external fsx high before clkx low mcbsp2 clkx int 28 ns m19 t su(fxh-ckxl ) setup time, external fsx high before clkx low mcbsp2 clkx ext 27 ns mcbsp3 clkx int 28 mcbsp3 clkx ext 27 mcbsp1 clkx int 3 mcbsp1 clkx ext 10 m20 t h(ckxl-fxh) hold time, external fsx high after clkx low mcbsp2 clkx int 3 ns m20 t h(ckxl-fxh) hold time, external fsx high after clkx low mcbsp2 clkx ext 3 ns mcbsp3 clkx int 3 mcbsp3 clkx ext 3 ? polarity bits clkrp = clkxp = fsrp = fsxp = 0. if the polarity of any of the signals is inverted, then the timing references of that signal are also inverted. ? p = 1/(base frequency) for mcbsp 1 and 3, or 1/(armper_ck clock frequency) in nanoseconds (ns) for mcbsp 2. base frequency is 12 or 13 mhz. for mcbsp1 and mcbsp2, the receiver clock and frame sync inputs are driven by fsx and clkx via internal loopback connections en abled via software configuration. electrical specifications 126 august 2002 ? revised august 2003 sprs197b table 5?15. mcbsp switching characteristics ?? no. parameter min max unit m0 t d(cksh-ckrxh) delay time, clks high to clkr/x high for internal clkr/x generated from clks input mcbsp1 clkr/x int 2 33 ns m1 t c(ckrx) cycle time, clkr/x clkr/x int 2p ns m2 t w(ckrxh) pulse duration, clkr/x high clkr/x int 0.45d 0.55d ns m3 t w(ckrxl) pulse duration, clkr/x low clkr/x int 0.45c 0.55c ns m4 t d(ckrh-frv) delay time, clkr high to internal fsr valid mcbsp2 clkr int ?1 13 ns m4 t d(ckrh-frv) delay time, clkr high to internal fsr valid mcbsp2 clkr ext ?3 24 ns mcbsp1 clkx int ?4 13 mcbsp1 clkx ext 7 39 m5 t d(ckxh-fxv) delay time, clkx high to internal fsx valid mcbsp2 clkx int ?1 4 ns m5 t d(ckxh-fxv) delay time, clkx high to internal fsx valid mcbsp2 clkx ext 2 24 ns mcbsp3 clkx int ?1 9 mcbsp3 clkx ext 2 37 mcbsp1 clkx int ?2 7 delay time, clkx high to dx valid. mcbsp1 clkx ext 7 40 m7 t d(ckxh-dxv) delay time, clkx high to dx valid. this applies to all bits except the first bit transmitted mcbsp2 clkx int 0 10 ns m7 t d(ckxh-dxv) this applies to all bits except the first bit transmitted when in data delay 0 (xdatdly=00b) mode. mcbsp2 clkx ext 3 27 ns when in data delay 0 (xdatdly=00b) mode. mcbsp3 clkx int ?1 10 mcbsp3 clkx ext 1 16 mcbsp1 fsx int 28 delay time, fsx high to dx valid ? mcbsp1 fsx ext 25 m9 t d(fxh-dxv) delay time, fsx high to dx valid ? only applies to first bit transmitted when in data mcbsp2 fsx int 30 ns m9 t d(fxh-dxv) only applies to first bit transmitted when in data delay 0 (xdatdly=00b) mode. mcbsp2 fsx ext 27 ns delay 0 (xdatdly=00b) mode. mcbsp3 fsx int 10 mcbsp3 fsx ext 27 ? polarity bits clkrp = clkxp = fsrp = fsxp = 0. if the polarity of any of the signals is inverted, then the timing references of that signal are also inverted. ? p = 1/(base frequency) for mcbsp 1 and 3, or 1/(armper_ck clock frequency) in ns for mcbsp 2. base frequency is 12 or 13 mhz. t=clkrx period = (1 + clkgdv) * p c=clkrx low pulse width = t/2 when clkgdv is odd or zero and = (clkgdv/2) * p when clkgdv is even d=clkrx high pulse width = t/2 when clkgdv is odd or zero and = (clkgdv/2 + 1) * p when clkgdv is even ? only dxena=0 is supported for all omap5910 mcbsps. electrical specifications 127 august 2002 ? revised august 2003 sprs197b (n?2) bit (n?1) (n?3) (n?2) bit (n?1) (n?4) (n?3) (n?2) bit (n?1) m18 m17 m18 m17 m17 m18 m16 m15 m4 m4 m14 m13 m3, m12 m1, m11 m2, m12 (rdatdly=10b) mcbspx.dr (rdatdly=01b) mcbspx.dr (rdatdly=00b) mcbspx.dr m cbspx.fsr/x ? mc bsp2.fsr (int) mc bspx.clkr/x ? (ext) m14 m13 mcbsp1.clks m0 ? for mcbsp1 and mcbsp3, the receiver clock and frame sync inputs are driven by fsx and clkx via internal loopback connections en abled via software configuration. the m13 and m14 descriptors are applicable only to mcbsp2. figure 5?18. mcbsp receive timings m7 m7 m7 m7 m9 (xdatdly=10b) mcbspx.dx (xdatdly=01b) mcbspx.dx (xdatdly=00b) mcbspx.dx (n?2) bit (n?1) bit 0 (n?4) bit (n?1) (n?3) (n?2) bit 0 (n?3) (n?2) bit (n?1) bit 0 m20 m14 m13 m3, m12 m1, m11 m2, m12 mcbspx.fsx m cbspx.fsx (int) mcbspx.clkx m5 m5 m19 (ext) figure 5?19. mcbsp transmit timings electrical specifications 128 august 2002 ? revised august 2003 sprs197b 5.9.2 mcbsp as spi master or slave timing table 5?16 to table 5?23 assume testing over recommended operating conditions (see figure 5?20 through figure 5?23). table 5?16. mcbsp as spi master or slave timing requirements (clkstp = 10b, clkxp = 0) ?? no. master slave unit no. min max min max unit m30 t su(drv-ckxl) setup time, mcbspx.dr valid before mcbspx.clkx low 15 2 ? 6p ns m31 t h(ckxl-drv) hold time, mcbspx.dr valid after mcbspx.clkx low 2 6 + 6p ns setup time, mcbspx.fsx low before mcbsp1 21 m32 t su(bfxl-ckxh ) setup time, mcbspx.fsx low before mcbspx.clkx high mcbsp2 5 ns m32 t su(bfxl-ckxh) mcbspx.clkx high mcbsp3 10 ns m33 t c(ckx) cycle time, mcbspx.clkx 2p 16p ns ? for all spi slave modes, clkg is programmed as 1/2 of the internal reference clock by setting clksm = clkgdv = 1. ? p = 1/(base frequency) for mcbsp 1 and 3, or 1/(armper_ck clock frequency) in ns for mcbsp 2. base frequency is 12 or 13 mhz. table 5?17. mcbsp as spi master or slave switching characteristics (clkstp = 10b, clkxp = 0) ?? no. parameter master slave unit no. parameter min max min max unit m24 t h(ckxl-fxl) hold time, mcbspx.fsx low after mcbspx.clkx low ? 0.45t 0.55t ns m25 t d(fxl-ckxh) delay time, mcbspx.fsx low to mcbspx.clkx high # 0.45c 0.55c ns m26 t d(ckxh-dxv) delay time, mcbspx.clkx high to mcbspx.dx valid ?1 7 3p + 2 5p+ 18 ns m29 t d(fxl-dxv) delay time, mcbspx.fsx low to mcbspx.dx valid 4p + 18 ns ? for all spi slave modes, clkg is programmed as 1/2 of the internal reference clock by setting clksm = clkgdv = 1. ? p = 1/(base frequency) for mcbsp 1 and 3, or 1/(armper_ck clock frequency) in ns for mcbsp 2. base frequency is 12 or 13 mhz. t = clkx period = (1 + clkgdv) * p c = clkx low pulse width = t/2 when clkgdv is odd or zero and = (clkgdv/2) * p when clkgdv is even ? fsrp = fsxp = 1. as a spi master, mcbspx.fsx is inverted to provide active-low slave-enable output. as a slave, the active-low signal input on mcbspx.fsx and mcbspx.fsr is inverted before being used internally. clkxm = fsxm = 1, clkrm = fsrm = 0 for master mcbsp clkxm = clkrm = fsxm = fsrm = 0 for slave mcbsp # mcbspx.fsx should be low before the rising edge of clock to enable slave devices and then begin a spi transfer at the rising edge of the m aster clock (mcbspx.clkx). bit 0 bit(n-1) (n-2) (n-3) (n-4) bit 0 bit(n-1) (n-2) (n-3) (n-4) clkx fsx dx dr m30 m26 m31 m24 m29 m25 lsb msb m32 m33 figure 5?20. mcbsp timing as spi master or slave: clkstp = 10b, clkxp = 0 electrical specifications 129 august 2002 ? revised august 2003 sprs197b table 5?18. mcbsp as spi master or slave timing requirements (clkstp = 11b, clkxp = 0) ?? no. master slave unit no. min max min max unit m39 t su(drv-ckxh) setup time, mcbspx.dr valid before mcbspx.clkx high 15 2 ? 6p ns m40 t h(ckxh-drv) hold time, mcbspx.dr valid after mcbspx.clkx high 2 6 +6p ns setup time, mcbspx.fsx low before mcbsp1 21 m41 t su(fxl-ckxh) setup time, mcbspx.fsx low before mcbspx.clkx high mcbsp2 5 ns m41 t su(fxl-ckxh) mcbspx.clkx high mcbsp3 10 ns m42 t c(ckx) cycle time, mcbspx.clkx 2p 16p ns ? for all spi slave modes, clkg is programmed as 1/2 of the internal reference clock by setting clksm = clkgdv = 1. ? p = 1/(base frequency) for mcbsp 1 and 3, or 1/(armper_ck clock frequency) in ns for mcbsp 2. base frequency is 12 or 13 mhz. table 5?19. mcbsp as spi master or slave switching characteristics (clkstp = 11b, clkxp = 0) ?? no. parameter master slave unit no. parameter min max min max unit m34 t h(ckxl-fxl) hold time, mcbspx.fsx low after mcbspx.clkx low ? 0.45c 0.55c ns m35 t d(fxl-ckxh) delay time, mcbspx.fsx low to mcbspx.clkx high # 0.45t 0.55t ns m36 t d(ckxl-dxv) delay time, mcbspx.clkx low to mcbspx.dx valid ?1 7 3p + 2 5p + 18 ns m38 t d(fxl-dxv) delay time, mcbspx.fsx low to mcbspx.dx valid d +20 4p + 18 ns ? for all spi slave modes, clkg is programmed as 1/2 of the internal reference clock by setting clksm = clkgdv = 1. ? p = 1/(base frequency) for mcbsp 1 and 3, or 1/(armper_ck clock frequency) in ns for mcbsp 2. base frequency is 12 or 13 mhz. t = clkx period = (1 + clkgdv) * p c = clkx low pulse width = t/2 when clkgdv is odd or zero and = (clkgdv/2) * p when clkgdv is even d = clkx high pulse width = t/2 when clkgdv is odd or zero and = (clkgdv/2 + 1) * p when clkgdv is even ? fsrp = fsxp = 1. as a spi master, mcbspx.fsx is inverted to provide active-low slave-enable output. as a slave, the active-low signal input on mcbspx.fsx and mcbspx.fsr is inverted before being used internally. clkxm = fsxm = 1, clkrm = fsrm = 0 for master mcbsp clkxm = clkrm = fsxm = fsrm = 0 for slave mcbsp # mcbspx.fsx should be low before the rising edge of clock to enable slave devices and then begin a spi transfer at the rising edge of the m aster clock (mcbspx.clkx). bit 0 bit(n-1) (n-2) (n-3) (n-4) bit 0 bit(n-1) (n-2) (n-3) (n-4) mcbspx.clkx mcbspx.fsx mcbspx.dx mcbspx.dr m35 m36 m40 m39 m38 m34 lsb msb m41 m42 figure 5?21. mcbsp timing as spi master or slave: clkstp = 11b, clkxp = 0 electrical specifications 130 august 2002 ? revised august 2003 sprs197b table 5?20. mcbsp as spi master or slave timing requirements (clkstp = 10b, clkxp = 1) ?? no. min master slave unit no. min min max min max unit m49 t su(drv-ckxh) setup time, mcbspx.dr valid before mcbspx.clkx high 15 2 ? 2p ns m50 t h(ckxh-drv) hold time, mcbspx.dr valid after mcbspx.clkx high 2 6 + 6p ns setup time, mcbspx.fsx low before mcbsp1 21 m51 t su(fxl-ckxl) setup time, mcbspx.fsx low before mcbspx.clkx low mcbsp2 5 ns m51 t su(fxl-ckxl) mcbspx.clkx low mcbsp3 10 ns m52 t c(ckx) cycle time, mcbspx.clkx 2p 16p ns ? for all spi slave modes, clkg is programmed as 1/2 of the cpu clock by setting clksm = clkgdv = 1. ? p = 1/(base frequency) for mcbsp 1 and 3, or 1/(armper_ck clock frequency) in ns for mcbsp 2. base frequency is 12 or 13 mhz. table 5?21. mcbsp as spi master or slave switching characteristics (clkstp = 10b, clkxp = 1) ?? no. parameter master slave unit no. parameter min max min max unit m43 t h(ckxh-fxl) hold time, mcbspx.fsx low after mcbspx.clkx high ? 0.45t 0.55t ns m44 t d(fxl-ckxl) delay time, mcbspx.fsx low to mcbspx.clkx low # 0.45d 0.55d ns m45 t d(ckxl-dxv) delay time, mcbspx.clkx low to mcbspx.dx valid ?1 7 3p + 2 5p + 18 ns m48 t d(fxl-dxv) delay time, mcbspx.fsx low to mcbspx.dx valid 4p + 18 ns ? for all spi slave modes, clkg is programmed as 1/2 of the internal reference clock by setting clksm = clkgdv = 1. ? p = 1/(base frequency) for mcbsp 1 and 3, or 1/(armper_ck clock frequency) in ns for mcbsp 2. base frequency is 12 or 13 mhz. t = clkx period = (1 + clkgdv) * p d = clkx high pulse width = t/2 when clkgdv is odd or zero and = (clkgdv/2 + 1) * p when clkgdv is even ? fsrp = fsxp = 1. as a spi master, mcbspx.fsx is inverted to provide active-low slave-enable output. as a slave, the active-low signal input on mcbspx.fsx and mcbspx.fsr is inverted before being used internally. clkxm = fsxm = 1, clkrm = fsrm = 0 for master mcbsp clkxm = clkrm = fsxm = fsrm = 0 for slave mcbsp # mcbspx.fsx should be low before the rising edge of clock to enable slave devices and then begin a spi transfer at the rising edge of the m aster clock (mcbspx.clkx). m51 m50 bit 0 bit(n-1) (n-2) (n-3) (n-4) bit 0 bit(n-1) (n-2) (n-3) (n-4) m cbspx.clkx m cbspx.fsx mcbspx.dx mcbspx.dr m44 m48 m45 m49 m43 lsb m52 msb figure 5?22. mcbsp timing as spi master or slave: clkstp = 10b, clkxp = 1 electrical specifications 131 august 2002 ? revised august 2003 sprs197b table 5?22. mcbsp as spi master or slave timing requirements (clkstp = 11b, clkxp = 1) ?? no. min master slave unit no. min min max min max unit m58 t su(drv-ckxl) setup time, mcbspx.dr valid before mcbspx.clkx low 15 2 ? 6p ns m59 t h(ckxl-drv) hold time, mcbspx.dr valid after mcbspx.clkx low 2 6 + 6p ns setup time, mcbspx.fsx low before mcbsp1 21 m60 t su(fxl-ckxl) setup time, mcbspx.fsx low before mcbspx.clkx low mcbsp2 5 ns m60 t su(fxl-ckxl) mcbspx.clkx low mcbsp3 10 ns m61 t c(ckx) cycle time, mcbspx.clkx 2p 16p ns ? for all spi slave modes, clkg is programmed as 1/2 of the internal reference clock by setting clksm = clkgdv = 1. ? p = 1/(base frequency) for mcbsp 1 and 3, or 1/(armper_ck clock frequency) in ns for mcbsp 2. base frequency is 12 or 13 mhz. table 5?23. mcbsp as spi master or slave switching characteristics (clkstp = 11b, clkxp = 1) ?? no. parameter master slave unit no. parameter min max min max unit m53 t h(ckxh-fxl) hold time, mcbspx.fsx low after mcbspx.clkx high ? 0.45d 0.55d ns m54 t d(fxl-ckxl) delay time, mcbspx.fsx low to mcbspx.clkx low # 0.45t 0.55t ns m55 t d(ckxh-dxv) delay time, mcbspx.clkx high to mcbspx.dx valid ?1 7 3p + 2 5p + 18 ns m57 t d(fxl-dxv) delay time, mcbspx.fsx low to mcbspx.dx valid c + 20 4p + 18 ns ? for all spi slave modes, clkg is programmed as 1/2 of the internal reference clock by setting clksm = clkgdv = 1. ? p = 1/(base frequency) for mcbsp 1 and 3, or 1/(armper_ck clock frequency) in ns for mcbsp 2. base frequency is 12 or 13 mhz. t = clkx period = (1 + clkgdv) * p c = clkx low pulse width = t/2 when clkgdv is odd or zero and = (clkgdv/2) * p when clkgdv is even d = clkx high pulse width = t/2 when clkgdv is odd or zero and = (clkgdv/2 + 1) * p when clkgdv is even ? fsrp = fsxp = 1. as a spi master, mcbspx.fsx is inverted to provide active-low slave-enable output. as a slave, the active-low signal input on mcbspx.fsx and mcbspx.fsr is inverted before being used internally. clkxm = fsxm = 1, clkrm = fsrm = 0 for master mcbsp clkxm = clkrm = fsxm = fsrm = 0 for slave mcbsp # mcbspx.fsx should be low before the rising edge of clock to enable slave devices and then begin a spi transfer at the rising edge of the m aster clock (mcbspx.clkx). bit 0 bit(n-1) (n-2) (n-3) (n-4) bit 0 bit(n-1) (n-2) (n-3) (n-4) mcbspx.clkx mcbspx.fsx mcbspx.dx mcbspx.dr m54 m58 m53 m55 m59 m57 lsb msb m60 m61 figure 5?23. mcbsp timing as spi master or slave: clkstp = 11b, clkxp = 1 electrical specifications 132 august 2002 ? revised august 2003 sprs197b 5.10 multichannel serial interface (mcsi) table 5?24 and table 5?25 assume testing over recommended operating conditions (see figure 5?24 and figure 5?25). table 5?24. mcsi timing requirements no. min max unit mc11 f op(clk) operating frequency, mcsix.clk slave b ? mhz mc12 t w(clkh) pulse duration, mcsix.clk high slave 0.45p ? 0.55p ? ns mc13 t w(clkl) pulse duration, mcsix.clk low slave 0.45p ? 0.55p ? ns mc14 t r(clk) rise time, mcsix.clk slave 12 ns mc15 t f(clk) fall time, mcsix.clk slave 12 ns mc16 t su(fsh-clkl) setup time, external mcsix.sync high before mcsix.clk low slave 18 ns mc16 t su(fsh-clkl) setup time, external mcsix.sync high before mcsix.clk low slave 18 ns mc17 t h(clkl-fsh) hold time, external mcsix.sync high after mcsix.clk low slave 6 ns mc17 t h(clkl-fsh) hold time, external mcsix.sync high after mcsix.clk low slave 6 ns mc18 t su(div-clkl) setup time, mcsix.din valid before mcsix.clk low master 27 ns mc18 t su(div-clkl) setup time, mcsix.din valid before mcsix.clk low slave 18 ns mc19 t h(clkl-div) hold time, mcsix.din valid after mcsix.clk low master 0 ns mc19 t h(clkl-div) hold time, mcsix.din valid after mcsix.clk low slave 6 ns ? p = mcsix.clk period [t c(clk) ] in nanoseconds. ? b = base frequency for omap5910 (12 or 13 mhz). table 5?25. mcsi switching characteristics no. parameter min max unit mc1 f op(clk) operating frequency, mcsix.clk master 0.5b ? mhz mc2 t w(clkh) pulse duration, mcsix.clk high master 0.45p ? 0.55p ? ns mc3 t w(clkl) pulse duration, mcsix.clk low master 0.45p ? 0.55p ? ns mc4 t d(clkh-fs) delay time, mcsix.clk high to mcsix.sync transition master 0 5 ns mc4 t d(clkh-fs) delay time, mcsix.clk high to mcsix.sync transition master 0 5ns mc7 t d(clkh-dov) delay time, mcsix.clk high to mcsix.dout valid master 0 5 ns mc7 t d(clkh-dov) delay time, mcsix.clk high to mcsix.dout valid slave 2 30 ns mc8 t en(clkh-do) enable time, mcsix.dout driven from mcsix.clk high master 0 ns mc8 t en(clkh-do) enable time, mcsix.dout driven from mcsix.clk high slave 2 ns ? p = mcsix.clk period [t c(clk) ] in nanoseconds. ? b = base frequency for omap5910 (12 or 13 mhz). electrical specifications 133 august 2002 ? revised august 2003 sprs197b bit (n) mc19 mc19 mc18 mc4 mc4 mc3 1/mc1 mc2 mcsix.din mcsix.sync mcsix.clk mc7 mc8 mcsix.dout bit (n) mc4 mc4 mcsix.sync (normal short) (alt. short) mc4 mc4 mcsix.sync (normal long) mcsix.sync (alt. long) (0) (0) mc4 mc4 mc18 (n?1) (n?1) figure 5?24. mcsi master mode timings (n?1) bit (n) mc19 mc19 mc18 mc16 mc15 mc14 mc13 1/mc11 mc12 mcsix.din mcsix.sync mcsix.clk mc7 mc8 mcsix.dout (n?1) bit (n) mcsix.sync (normal short) (alt. short) mc17 mcsix.sync (normal long) mcsix.sync (alt. long) (0) (0) m17 mc16 mc17 mc16 mc16 mc18 mc17 figure 5?25. mcsi slave mode timings electrical specifications 134 august 2002 ? revised august 2003 sprs197b 5.11 camera interface timings table 5?26 assumes testing over recommended operating conditions (see figure 5?26). table 5?26. camera interface timing requirements no. min max unit c1 1 / [ t c(lckh?hsv) ] operating frequency, cam.lclk 13 mhz c2 1 / [ t c(xckh?hsv) ] operating frequency, cam.exclk 24 mhz c3 t w(lck) pulse duration, cam.lclk high or low 0.45p ? 0.55p ? ns c5 t su(lckh?dv) setup time, cam.d[7:0] data valid before cam.lclk high 1 ? ns c6 t h(dv?lckh) hold time, cam.d[7:0] data valid after cam.lclk high 9? ns c7 t su(lckh?dv) setup time, cam.vs/cam.hs active before cam.lclk high 1 ? ns c8 t h(dv?clkh) hold time, cam.vs/cam.hs active after cam.lclk high 9? ns ? p = period of cam.lclk in nanoseconds (ns). ? polarity of cam.lclk is selectable via the polclk bit in the ctrlclock register. although data is latched on rising cam.lclk in the timing diagrams, these timing parameters also apply to falling cam.lclk when polclk = 1. cam.lclk cam.hs cam.d[7:0] cam.vs u1 y1 v1 yn c7 c6 c7 c8 c8 c5 c6 c5 c3 c3 c1 figure 5?26. camera interface timings electrical specifications 135 august 2002 ? revised august 2003 sprs197b 5.12 lcd controller timings table 5?27 assumes testing over recommended operating conditions (see figure 5?27 and figure 5?28). table 5?27. lcd controller switching characteristics ? no. parameter min max unit l1 t d(clkh?hsv) delay time, lcd.pclk high to lcd.hs transition 1 11 ns l2 t d(clkl?hsv) delay time, lcd.pclk low to lcd.hs transition 1 11 ns l3 t d(clkh?vsv) delay time, lcd.pclk high to lcd.vs transition 1 11 ns l4 t d(clkl?vsv) delay time, lcd.pclk low to lcd.vs transition 1 11 ns l5 t d(clkh?pv) delay time, lcd.pclk high to pixel data valid (lcd.p[15:0]) 11 ns l6 t d(clkh?piv) delay time, lcd.pclk high to pixel data invalid (lcd.p[15:0]) 1 ns l7 t d(clkl?pv) delay time, lcd.pclk low to pixel data valid (lcd.p[15:0]) 11 ns l8 t d(clkl?piv) delay time, lcd.pclk low to pixel data invalid (lcd.p[15:0]) 1 ns l9 t d(clkl?acv) delay time, lcd.pclk high to lcd.ac transition 1 5+p ? ns l10 t d(clkl?acv) delay time, lcd.pclk low to lcd.ac transition 1 5+p ? ns ? although timing diagrams illustrate the logical function of the tft mode, static timings apply to all supported modes of operat ion. likewise, lcd.hs, lcd.vs, and lcd.ac are shown as active-low, but each may optionally be configured as active-high. ? p = period of internal undivided pixel clock lcd.pclk lcd.vs lcd.p[15:0] lcd.ac lcd.hs l4 l9 l5 d1 d2 d3 dn l6 l9 l4 l2 l2 hsw ? vsw ? vfp ? hfp ? hbp ? ppl ? ? delays for hsw (lcd.hs width), vsw (lcd.vs width), vfp (vertical front porch), hfp (horizontal front porch), hbp (horizontal back porc h) and ppl (pixels per line) are programmable in number of lcd.pclk cycles via the lcd configuration registers. figure 5?27. tft mode (lcd.hs/lcd.vs on falling and lcd.px on rising lcd.pclk) electrical specifications 136 august 2002 ? revised august 2003 sprs197b lcd.pclk lcd.vs lcd.p[15:0] lcd.ac lcd.hs l3 l7 d1 d2 d3 dn l8 l3 l1 l1 hsw ? hbp ? ppl ? l10 l10 vsw ? vfp ? hfp ? ? delays for hsw (lcd.hs width), vsw (lcd.vs width), vfp (vertical front porch), hfp (horizontal front porch), hbp (horizontal back porc h) and ppl (pixels per line) are programmable in number of lcd.pclk cycles via the lcd configuration registers. figure 5?28. tft mode (lcd.hs/lcd.vs on rising and lcd.px on falling lcd.pclk) electrical specifications 137 august 2002 ? revised august 2003 sprs197b 5.13 multimedia card/secure digital (mmc/sd) timings table 5?28 and table 5?29 assume testing over recommended operating conditions (see figure 5?29 through figure 5?32). table 5?28. mmc/sd timing requirements no. min max unit m1 t su(cmdv?clkh) setup time, mmc.cmd valid before mmc.clk high 12 ns m2 t h(clkh?cmdv) hold time, mmc.cmd invalid after mmc.clk high 2 ns m3 t su(datv?clkh) setup time, mmc.datx valid before mmc.clk high 12 ns m4 t h(clkh?datv) hold time, mmc.datx invalid after mmc.clk high 2 ns table 5?29. mmc/sd switching characteristics no. parameter min max unit m7 t c(clk) cycle time, mmc.clk 41.7 ns m7 t c(clk) cycle time, mmc.clk 5.31 us m8 t w(clkh) pulse duration, mmc.clk high 20 ? ns m9 t w(clkl) pulse duration, mmc.clk low 20 ? ns m10 t d(clkh?cmd) delay time, mmc.clk high to mmc.cmd transition 4 48 ns m11 t d(clkh?dat) delay time, mmc.clk high to mmc.datx transition 4 48 ns ? mmc.clk period and pulse duration depends upon software configuration. mmc.clk mmc.cmd xmit valid m10 m10 m10 m10 valid valid start end m9 m8 m7 figure 5?29. mmc/sd host command timings mmc.clk mmc.cmd m7 xmit valid valid valid start end m1 m1 m2 m9 m8 m2 figure 5?30. mmc/sd card response timings electrical specifications 138 august 2002 ? revised august 2003 sprs197b mmc.clk mmc.datx m11 m11 m11 m11 end start d0 d1 d2 dx m9 m8 m7 figure 5?31. mmc/sd host write timings mmc.clk mmc.datx m4 m3 end start d0 d1 d2 dx m3 m4 m7 m9 m8 figure 5?32. mmc/sd host read and card crc status timings electrical specifications 139 august 2002 ? revised august 2003 sprs197b 5.14 i 2 c timings table 5?30 assumes testing over recommended operating conditions (see figure 5?33). table 5?30. i 2 c signals (i2c.sda and i2c.scl) switching characteristics no. parameter standard mode fast mode unit no. parameter min max min max unit ic1 t c(scl) cycle time, i2c.scl 10 ? 2.5 s ic2 t su(sclh-sdal) setup time, i2c.scl high before i2c.sda low (for a repeated start condition) 4.7 0.6 s ic3 t h(scll-sdal) hold time, i2c.scl low after i2c.sda low (for a repeated start condition) 4 0.6 s ic4 t w(scll) pulse duration, i2c.scl low 4.7 1.3 s ic5 t w(sclh) pulse duration, i2c.scl high 4 0.6 s ic6 t su(sda-sdlh) setup time, i2c.sda valid before i2c.scl high 250 ? 100 ns ic7 t h(sda-sdll) hold time, i2c.sda valid after i2c.scl low (for i 2 c bus devices) 0 0 0.9 s ic8 t w(sdah) pulse duration, i2c.sda high between stop and start conditions 4.7 1.3 s ic9 t r(sda) rise time, i2c.sda 1000 300 ns ic10 t r(scl) rise time, i2c.scl 1000 300 ns ic11 t f(sda) fall time, i2c.sda 300 300 ns ic12 t f(scl) fall time, i2c.scl 300 300 ns ic13 t su(sclh-sdah) setup time, i2c.scl high before i2c.sda high (for stop condition) 4.0 0.6 s ic14 t w(sp) pulse duration, spike (must be suppressed) 0 50 ns ic15 c b capacitive load for each bus line 400 400 pf ? in the master-only i 2 c operating mode of omap5910, minimum cycle time for i2c.scl is 12 s. ? the maximum t h(scll-sdal) has only to be met if the device does not stretch the low period (t w(scll) ) of the i2c.scl signal. c b = the total capacitance of one bus line in pf. ic10 ic8 ic4 ic3 ic7 ic12 ic5 ic6 ic14 ic2 ic3 ic13 stop start repeated start stop i2c.sda i2c.scl ic1 notes: a. a device must internally provide a hold time of at least 300 ns for the i2c.sda signal (referred to the v ihmin of the i2c.scl signal ) to bridge the undefined region of the falling edge of i2c.scl. b. the maximum t h(scll?sdal) has only to be met if the device does not stretch the low period (t w(scll) ) of the i2c.scl signal. c. a fast-mode i 2 c-bus device can be used in a standard-mode i 2 c-bus system, but the requirement t su(sda?sdlh) ? 250 ns must then be met. this will automatically be the case if the device does not stretch the low period of the i2c.scl signal. if such a device does stretch the low period of the i2c.scl signal, it must output the next data bit to the i2c.sda line t r max + t su(sda?sdlh) = 1000 + 250 = 1250 ns (according to the standard-mode i 2 c-bus specification) before the i2c.scl line is released. d. c b = total capacitance of one bus line in pf. if mixed with fast-mode devices, faster fall times are allowed. figure 5?33. i 2 c timings electrical specifications 140 august 2002 ? revised august 2003 sprs197b 5.15 universal serial bus (usb) timings all omap5910 usb interfaces are compliant with the universal serial bus specification, revision 2.0 . table 5?31 assumes testing over recommended operating conditions (see figure 5?34). table 5?31. usb integrated transceiver interface switching characteristics no. parameter low speed 1.5 mbps full speed 12 mbps unit no. parameter min max min max unit u1 t r rise time, usb.dp and usb.dm signals ? 75 ? 300 ? 4 ? 20 ? ns u2 t f fall time, usb.dp and usb.dm signals ? 75 ? 300 ? 4 ? 20 ? ns u3 t rfm rise/fall time matching ? 80 ? 125 ? 90 ? 111.11 ? % u4 v crs output signal cross-over voltage ? 1.3 ? 2.0 ? 1.3 ? 2.0 ? v u5 t jr differential propagation jitter ?25 25 ?2 2 ns u6 f op operating frequency ? 1.5 12 mhz ? low speed: c l = 200 pf, full speed: c l = 50 pf ? t rfm = (t r /t f ) x 100 t jr = t px(1) ? t px(0) ? f op = 1/t per v ol u1 u2 v crs v oh 90% 10% ref clock ? usb.dm usb.dp t px(0) t px(1) t per ? t jr ? ?ref clock? is not an actual device signal, but an ideal reference clock against which relative timings are specified. ref cloc k is assumed to be 12 mhz for full-speed mode or 1.5 mhz for low-speed mode). figure 5?34. usb integrated transceiver interface timings electrical specifications 141 august 2002 ? revised august 2003 sprs197b 5.16 microwire interface timings table 5?32 and table 5?33 assume testing over recommended operating conditions (see figure 5?35). table 5?32. microwire timing requirements no. min max unit w5 t su(sdi?sclk) setup time, uwire.sdi valid before uwire.sclk active edge ? 21 ns w6 t h(sclk?sdi) hold time, uwire.sdi invalid after uwire.sclk active edge ? 6 ns ? polarity of uwire.sclk and the active clock edge (rising or falling) on which sdo data is driven and sdi data is latched is all software configurable. these timings apply to all configurations regardless of uwire.sclk polarity and which clock edges are used to drive output data and capture input data. table 5?33. microwire switching characteristics no. parameter min max unit w1 f op(sclk) operating frequency, uwire.sclk 3 mhz w2 t w(sclk) pulse duration, uwire.sclk high/low 0.45p ? 0.55p ? ns w3 t d(sclk?sdo) delay time, uwire.sclk active edge to uwire.sdo transition ? ?3 6 ns w4 t d(cs?sclk) delay time, uwire.csx active to uwire.sclk active ? 1.5p ? ns ? polarity of uwire.sclk and the active clock edge (rising or falling) on which sdo data is driven and sdi data is latched is all software configurable. these timings apply to all configurations regardless of uwire.sclk polarity and which clock edges are used to drive output data and capture input data. ? p = uwire.sclk cycle time in ns. uwire.sclk uwire.csx w2 w2 uwire.sdo w3 [1/w1] uwire.sdi valid valid valid valid valid valid w3 w5 w6 w4 w4 note: the polarities of uwire.csx and uwire.sclk and the active uwire.sclk edges on which sdo is driven and sdi is sampled are a ll software configurable. figure 5?35. microwire timings electrical specifications 142 august 2002 ? revised august 2003 sprs197b 5.17 hdq/1-wire interface timings table 5?34 and table 5?35 assume testing over recommended operating conditions (see figure 5?36 through figure 5?39). table 5?34. hdq/1-wire timing requirements ? min max unit h1 t c cycle time, master read 190 250 s h2 t v read one data valid after hdq low 32 50 s h3 t v read zero data hold after hdq low 80 145 s h4 t v response time from hdq slave device omap5910 base frequency = 12 mhz 190 320 s h4 t v response time from hdq slave device omap5910 base frequency = 13 mhz 190 303 s w1 t c cycle time, master read 190 s w2 t v read data valid after hdq low (master sample window) 12 13.6 s w3 t dis recovery time after slave device inactive 1 s ? hdq timing is omap5910 default. 1-wire timing is selectable through software. table 5?35. hdq/1-wire switching characteristics parameter min max unit h5 t c cycle time, master write 190 s h6 t d write one data valid after hdq low 32 50 s h7 t d write zero data hold after hdq low omap5910 base frequency = 12 mhz 100 145 s h7 t d write zero data hold after hdq low omap5910 base frequency = 13 mhz 92 145 s h8 t w pulse width, hdq low for break pulse (reset) 190 s h9 t w pulse width, hdq high for break pulse recovery 40 s w4 t c cycle time, master write 190 s w5 t d write zero master inactive after hdq low 15 90 s w6 t d write one master inactive after hdq low 1.1 1.4 s w7 t dis recovery time after master inactive 1 s electrical specifications 143 august 2002 ? revised august 2003 sprs197b hdq h2 h3 h1 read 0 read 1 figure 5?36. omap5910 hdq interface reading from hdq slave device hdq h6 h7 h5 write 0 write 1 figure 5?37. omap5910 hdq interface writing to hdq slave device 7 (msb) 0 (lsb) 0 (lsb) 7 (msb) break 1 6 register address command byte (written by omap5910) 1 6 data byte (received by omap5910 from slave) h4 hdq figure 5?38. typical communication between omap5910 hdq and hdq slave h11 h12 hdq h8 h9 hdq figure 5?39. hdq/1-wire break (reset) timing glossary 144 august 2002 ? revised august 2003 sprs197b 6 glossary acronym definition 1-wire a serial protocol defined by dallas semiconductor corporation aac advanced audio coding (standard) (iso/iec 13818-7) ac97 interface standard for codecs alu arithmetic/logic unit amr adaptive multi-rate asram asynchronous static ram au address unit bcd binary coded decimal bga ball grid array cmos complementary metal oxide semiconductor cp15 coprocessor 15 crc cyclic redundancy check csl chip support library cts clear-to-send daram dual-access ram dct discrete cosine transform dma direct memory access dpll digital phase-locked loop dsp digital signal processor dsplib dsp library dsr data-set-ready dtr data-terminal-ready du data unit emiff external memory interface fast emifs external memory interface slow ep endpoint esd electrostatic discharge etm fac frame adjustment counter fft fast fourier transform fifo first-in first out fiq fast interrupt request gprs general packet radio service gsm global system for mobile communications h.26x an itu-tss standard hbm human body model hbp horizontal back porch glossary 145 august 2002 ? revised august 2003 sprs197b definition acronym hdq a single-wire serial interface protocol defined by benchmarq ? controls inc. hfp horizontal front porch hom host-only mode hs high-speed i-cache instruction cache i 2 c inter-integrated circuit i 2 s inter-ic sound (specification) idct inverse discrete cosine transform i/f interface ifr interrupt flag register imglib image/video processing library imif internal memory interface imr interrupt mask register iom-2 isdn oriented modular interface revision 2 irda infrared data adapter irq low-priority interrupt request iu instruction unit jpeg joint photographic experts group ? standard for compressed still-picture data lb local bus lcd liquid crystal display lpg led pulse generator lsb least significant bit lvcmos low-voltage cmos mac multiply-accumulate mcsi multichannel serial interface mcbsp multichannel buffered serial port mmc multimedia card mmc/sd multimedia card/secure digital mmu memory management unit mpeg moving picture experts group ? proposed standard for compressed video data mpu microprocessor unit mpui microprocessor unit interface mpuio microprocessor unit i/o msb most significant bit mvip multi-vendor integration protocol odm original design manufacturer oem original equipment manufacturer ohci open host controller interface os operating system benchmarq is a trademark of texas instruments. glossary 146 august 2002 ? revised august 2003 sprs197b definition acronym ppl pixels per line pu program unit pwl pulse-width light pwt pulse-width tone risc reduced instruction set computer rtc real-time clock rts request-to-send sam shared-access mode saram single-access ram sd secure digital sdram synchronous dynamic ram sdw short distance wireless sir slow infrared spi serial peripheral interface sram static ram srg sample rate generator stn super twisted nematic t1/e1 t1 is a digital transmission link with a capacity of 1.544 mbps. it uses two pairs of nor- mal twisted-wires and can handle 24-voice conversations, each digitized using mu-law coding at 64 kbps. t1 is used in usa, canada, hong kong, and japan. e1 is a digital transmission link with a capacity of 2.048 mbps. it is the european equivalent of t1. it can handle 30-voice conversations, each digitized using a-law coding at 64 kbps. tap test access port tc traffic controller tft thin-film transistor ti texas instruments tipb ti peripheral bus tlb translation look-aside buffer ttb translation table base uart universal asynchronous receiver/transmitter ulpd ultra low-power device url uniform resource locator usb universal serial bus usb2.0 universal serial bus specification revision 2.0 vfp vertical front porch vivt virtual index virtual tag wb write buffer wdt watchdog timer wma windows media audio wmv windows media video mechanical data 147 august 2002 ? revised august 2003 sprs197b 7 mechanical data 7.1 gzg ball grid array mechanical data gzg (s-pbga-n289) plastic ball grid array 0,08 m ? 0,05 0,50 0,50 1,20 max 0,85 0,25 0,35 0,30 0,20 0,95 12,10 11,90 sq 4173512-6/d 11/01 seating plane 8 l b a 1 f d c e h k g j 3 24 7 5 6 r m p n v t u w aa y 15 11 9 10 13 12 14 18 17 16 21 19 20 10,00 typ a1 corner bottom view notes: a. all linear dimensions are in millimeters. b. this drawing is subject to change without notice. c. microstar bga ? configuration figure 7?1. omap5910 289-ball microstar bga ? plastic ball grid array (gzg) package microstar bga is a trademark of texas instruments. mechanical data 148 august 2002 ? revised august 2003 sprs197b 7.2 gdy ball grid array mechanical data gdy (s-pbga-n289) plastic ball grid array package 4204662/a 09/02 seating plane 0,60 0,40 a 1 1,00 1,00 16,00 typ 0,30 0,50 18,80 19,20 sq 2 b 2,32 max 4 3 6 5 8 7 10 9 12 11 14 13 16 15 17 c d e f g h j k l m n p r t u bottom view a1 corner 0,10 0,15 17,30 17,70 sq 1,12 1,22 notes: a. all linear dimensions are in millimeters. b. this drawing is subject to change without notice. figure 7?2. omap5910 289-ball plastic ball grid array (gdy) package |
Price & Availability of OMAP5910DSP
 |
|
|
|
|
All Rights Reserved © IC-ON-LINE 2003 - 2022 |
| [Add Bookmark] [Contact Us] [Link exchange] [Privacy policy] |
|
Mirror Sites : [www.datasheet.hk]
[www.maxim4u.com] [www.ic-on-line.cn]
[www.ic-on-line.com] [www.ic-on-line.net]
[www.alldatasheet.com.cn]
[www.gdcy.com]
[www.gdcy.net] |